C4 Model: Google Maps for Software Architecture
Four zoom levels that transform confusing boxes-and-lines into architecture diagrams that actually communicate. Context → Container → Component → Code.
The Diagram Problem
Ever opened an architecture diagram and thought: "Who is this for?" "Why is everything in one box?" "Is this database inside the system or outside?" That confusion exists because there's no consistent language for software diagrams.
The Google Maps Analogy
Google Maps doesn't show you street-level detail when you're planning a cross-country trip. And it doesn't show you the whole country when you're finding a parking spot. It zooms to the right level for your current need.
The C4 model works the same way. Created by Simon Brown, it provides four "zoom levels" for software architecture—each showing the right detail for different audiences and purposes.
The Four Zoom Levels
Each level answers different questions for different audiences. Start at Context, zoom in only as far as needed.
Level 1: System Context Diagram
Who uses this? What does it connect to?
Audience
Everyone (technical and non-technical)
Shows
Your system as a black box + external actors and systems
Elements You'll See
Example
Internet Banking System used by Personal Customers, connects to Mainframe Banking System and Email System
Analogy
🗺️ Country level - "Australia is here, connected to these neighbors"
Context
- •Stakeholder presentations
- •Project kickoffs
- •System design interviews (start here!)
- •Business documentation
- •Integration planning
Container
- •Development team onboarding
- •Deployment planning
- •Technology decisions
- •DevOps/infrastructure discussions
- •Cost estimation
Component
- •Sprint planning
- •Code reviews
- •Feature design
- •Debugging complex issues
- •Team handoffs
Code
- •Complex algorithm documentation
- •API contract design
- •Legacy code understanding
- •Usually auto-generated from code
- •(Often skipped in practice)
Why C4 Matters for Your Organisation
Architecture diagrams that nobody understands are worse than no diagrams at all. C4 solves this by giving everyone a common language.
New team members understand the system in hours, not weeks. Start with Context, zoom in as needed.
When everyone sees the same picture, decisions are faster and safer. No more "I thought it worked differently."
Text-based diagrams live with your code. They stay current because updating them is trivial.
Related Modeling Standards
C4 Resources
Need Help Documenting Your Architecture?
We help teams create clear, maintainable architecture documentation using C4 and related standards. From discovery workshops to living documentation.