Chapter 4. Container Diagram
Once you’ve created a system context diagram and you understand how your software system fits into the overall system landscape, the next step is to describe the applications and data stores (the C4 containers) that exist within the boundary of the software system. This is the purpose of the C4 container diagram and the topic of this chapter.
Key Aspects of the Container Diagram
To understand why and how to use container diagrams, keep in mind their intent, scope, content, use cases, and audience.
Intent
A container diagram helps you to answer the following questions:
-
How has the software system been decomposed into applications and data stores?
-
What are the responsibilities of those applications and data stores?
-
What are the primary technology choices (e.g., programming languages and products) used to implement those applications and data stores?
-
How do the applications and data stores communicate with one another?
-
As a software engineer, where do I need to write code to add a feature?
An important point to note ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access