Whiteboard arrows between service boxes with citrus tape

Node.js · Advanced · Hybrid

Service Boundaries Workshop

Carve modules that align with deployment units without over-splitting early.

Microservices hype created brittle sprawl. This workshop rewards small, reversible steps grounded in traffic facts—not buzzwords.

Duration: 4 weeks

Tuition (informational): 8,800,000 VND

Final quotes come from admissions. See Money-Back Policy for eligibility.

What ships in the syllabus

  • Heuristic for synchronous vs asynchronous coupling
  • Domain event sketching on a whiteboard template
  • Library extraction exercise with semver discipline
  • Load test smoke to validate boundary assumptions
  • Rollback drills for partial deploys
  • Mentor review of your current repo map
  • Reading packet of postmortems (redacted)

Outcomes we actually assess

  1. Present a boundary proposal with two tradeoff slides
  2. Run a smoke load on a split module
  3. Capture a rollback checklist tailored to your org
Portrait for An Dang

An Dang

Backend instructor emphasizing observability and structured logging.

FAQ — including what we skip

Kubernetes required?

No. We discuss orchestration conceptually; labs use local compose.

Team attendance?

Discounts exist for pairs, but exercises are still submitted individually.

Is vendor tech covered?

We stay vendor-neutral on message brokers beyond AMQP basics.

Experience notes

“The coupling worksheet exposed our hidden chatty calls.”
Quan · Logistics API team · 5/5
“Postmortem readings were grim but grounded the sessions.”
Ha · Tech lead