✏️ Explanatory Question
What are common mistakes when drawing a system architecture diagram?
No previous question
No next question
Watch for these.
- Too much detail too early - class level detail in a diagram meant to show services.
- Unlabelled arrows - the reader cannot tell HTTP from a queue message, or sync from async.
- No datastore ownership - several services drawn writing to one shared database, which quietly couples them.
- Missing the client - the diagram starts at the load balancer and hides CDN or mobile caching decisions.
- Drawing only the happy path - no indication of what happens when a dependency is down.
- Boxes with vague names - "Backend" or "Service" instead of a clear responsibility.
No previous question
No next question