A service diagram is useful when it explains decisions, not when it simply contains many boxes.

What this note will cover

  • Separating web, API and realtime responsibilities
  • Workers, schedulers and backups as their own operating concerns
  • Search and memory services and their data and access questions
  • Documenting boundaries so a new engineer can follow them

Why it matters

Clear service responsibilities make changes safer to review, test and operate.