The containers inside one software system and who calls each Drawn once the context diagram has fixed the boundary, a C4 container view opens the system into the applications, services and data stores it runs, and labels who calls what, so the public-facing web app that carries the heaviest hosting and security review is clear at a glance.
The containers inside one software system and who calls each
A C4 container diagram for a distribution operator's LTDS publication system. A dashed system boundary encloses four flat containers in a diamond: the capacity web app as the public entry point, a capacity API, a capacity store of record, and a publication pipeline. Above it a connections customer views the web app and an Ofgem analyst pulls data from the API. Both entry containers read the store, the pipeline writes it, and it reads geography from the GIS and ratings from the asset register.
System boundary: LTDS publication system
Connections customer Checks where capacity exists Ofgem analyst Reviews compliance and data Person Capacity web app Tables, maps and downloads Public entry point Container Capacity API Machine readable capacity Programmatic entry point Container Capacity store Published tables and history System of record Container Publication pipeline Builds each LTDS release Scheduled batch job GIS Network geography and routes External Asset register Ratings and asset records External Views capacity in Pulls data from Reads Reads Writes Reads geography from Reads ratings from People who use the system External source systems it does not own
