Phase C, Information Systems ArchitectureDerived from C4 Model

C4 Container Diagram

Open one software system into the applications, services and data stores it runs, with named relationships, so hosting and integration decisions start from a shared picture.

All tools

C4 container view: the moving parts inside one software system

A C4 container diagram zooms one level into the system boundary: the applications, services and data stores it is built from, who uses each entry point, and which source systems feed it.

C4 container view: the moving parts inside one software system A C4 model container diagram for the LTDS publication system of a distribution network operator. Inside the dashed system boundary are four containers: a capacity web app with tables, maps and downloads, a capacity API serving machine readable data, a capacity store holding published tables and history, and a publication pipeline that builds each LTDS release. A connections customer views capacity in the web app and an Ofgem analyst pulls data from the API. Both entry containers read the store, the pipeline writes it, and the pipeline reads geography from the GIS and ratings from the asset register. SYSTEM BOUNDARY LTDS publication system PERSON Connections customer Checks where capacity exists PERSON Ofgem analyst Reviews compliance and data CONTAINER Capacity web app Tables, maps and downloads CONTAINER Capacity API Machine readable capacity CONTAINER Capacity store Published tables and history CONTAINER Publication pipeline Builds each LTDS release EXTERNAL SYSTEM GIS Network geography and routes EXTERNAL SYSTEM Asset register Ratings and asset records Views capacity in Pulls data from reads reads writes Reads geography from Reads ratings from Source: Simon Brown, c4model.com

Draw it after the context diagram has fixed the boundary. Each container is something that runs or stores data; the labelled arrows record who calls what, so hosting, security and team conversations all start from the same picture.

Once the context diagram has fixed the system boundary and the conversation turns to what runs inside it.

What you need and what you get

You'll need

  • The agreed system boundary from the context diagram
  • The containers inside it and the source systems that feed them

You'll get

  • A container diagram inside the system boundary
  • Named relationships for every call, read and write

Taught in

No course modules linked yet.

Derived from

  • Simon BrownSimon Brown, C4 model, level 2 ContainerSource