liveBook · Manning

C4 model

As explained in Developer Experience on Kubernetes

The C4 model is a hierarchical software architecture modeling approach based on system context, containers, components, and code diagrams.

The C4 model provides a practical way to visualize software architecture at different levels of detail. Start with who uses a system and what it interacts with, then zoom into the applications and data services that implement it. section 1.4.1

Use the model to move from stakeholder-friendly context to developer-oriented structure:

  • A system context diagram shows users, the system, and other systems it interacts with without exposing internal technologies. section 1.4.1
  • A container diagram zooms into the system, showing high-level applications or data services, their responsibilities, and their interactions. section 1.4.1
  • In C4 terminology, a container means an application or data service; it does not mean a Docker or Podman container. section 1.4.1

MinSalus architecture

A patient uses MinSalus to book appointments and receive schedule updates. The context diagram presents the patient and MinSalus as the main abstractions. The container diagram then identifies elements such as the Patient Portal, session store, and Appointment Service, clarifying their responsibilities and relationships. section 1.4.1

Figure 1.6 The system context diagram for MinSalus, following the C4 model.

Inspect the system context diagram to see how users, the system, and external interactions are represented for a broad audience. section 1.4.1

Figure 1.7 The container diagram for MinSalus, following the C4 model.

Inspect the container diagram to see how internal applications and data services are decomposed for development work. section 1.4.1

How Developer Experience on Kubernetes covers it

How deep it goes
Explains system context and container diagrams with their abstractions, audiences, and interactions, while deferring internal implementation technologies at context level.
Examples
Uses MinSalus, a patient, the Patient Portal, a session store, and the Appointment Service as diagrammed architecture examples.
What it assumes
Assumes familiarity with software systems and users while defining the C4 abstractions and diagram purposes directly.
What you can do after
Evaluate architecture by identifying system boundaries, users, applications, data services, responsibilities, and interactions at appropriate detail levels.
How it connects
Connects software architecture with system context diagrams, container diagrams, applications, data services, users, and external systems.

Also explained in

Compare how 3 books explain C4 model →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Developer Experience on Kubernetes. The section links point to the parts of the book it draws on.