Diagrams
System architecture diagram template
Services, data stores and the arrows between them, for design reviews and onboarding.
What it is
A system architecture diagram shows the parts of a software system and how they connect. Apps, services, queues, databases and outside providers each get a box, and arrows show which part calls which.
When to use it
- In a design review, before you build something new
- To bring new engineers up to speed on an existing system
- When you plan a migration and need to see what depends on what
How to run it
- 01
Start where users come in
Put the app or website people use in the first box.
- 02
Add services and data stores
One box per service, database or third-party provider. Name the technology when it helps, like Postgres.
- 03
Draw the calls
Connect each box to the parts it calls. Add a short label to an arrow when the data or protocol is not obvious.
- 04
Mark the weak spots
Put a sticky note next to anything that would take the whole system down if it failed. Those are the topics for the review.
Opens a new board from this prompt:
"System architecture for a food delivery app with a mobile app, order service, payment provider and driver tracking"