Architecture, distribution and integration
Hybrid local/cloud deployment
A deployment split across on-premises and cloud environments: what runs where, and the links between them.
ddn@1New DDN source
Why use it?
Hybrid designs fail at the seams; the seam list is the point of the diagram.
When it helps
Planning or reviewing any system spanning local and cloud infrastructure.
How to read it
- Environment boundaries are the thick lines — everything crossing them is an explicit link.
- Data gravity arrows point where state lives, not where compute happens.
What you need
- The environments
- Component placements
- The cross-boundary links and their protocols
Things to check
- Do not leave the boundary link unnamed — it is usually the riskiest part.
- Do not duplicate a component in both environments without saying which is authoritative.
Scope of this diagram
Structural documentation; no latency, failover or cost model is implied.
Work with the converted example
- Open the viewer and select
diagram. 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.