Architecture, distribution and integration
C4 deployment diagram
C4-style deployment: nodes and where the containers actually run.
c4.deployment@1New DDN source
Why use it?
The container view says what exists; the deployment view says where it lives.
When it helps
Release planning, environment reviews, incident reading.
How to read it
- Placement is a fact per environment; paths between nodes are the links operations watches.
- A container missing from the map is not deployed (or not documented).
What you need
- The environments
- Container placements
- The operational links
Things to check
- Do not assume dev matches production on paper.
- Do not hide a placement because it is embarrassing.
Scope of this diagram
C4-style equivalent with tag-chip styling; no live discovery.
Work with the converted example
- Open the viewer and select
deployment. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.