Designing for Service Boundaries

Good service boundaries reduce coupling and make ownership clearer.

Signals of a healthy boundary

• A team can evolve it without waiting on multiple approvals.
• Inputs and outputs are explicit and versioned.
• Runtime metrics are attributable to a single owner.

Minimal contract example

type AppointmentRequest = {
  patientId: string;
  requestedAt: string;
};