Planned landscape
Components
What is deployed, and how does a use case flow through it?
Every deployed component, and for each one the inner flow of a main use case as it actually ran — recorded from a real execution rather than drawn from memory.
What it will show
- A catalogue of what is actually deployed, per environment, rather than what was once designed.
- For each component, the inner flow of a main use case: the call sequence as it ran, not as it was intended.
- The queries a use case really issues, and the boundaries it really crosses.
- The gap between the drawn architecture and the executed one — which is the only place drift is ever visible.
Where it stands
- Status
- Planned
- Rendered from
- arch-appmap
arch-appmap already renders AppMap traces; what is missing is the catalogue in front of them and the use-case selection behind each component.
A landscape earns a panel when something renders it. Until then it says so, because a link to an empty page is worse than one that admits it is not built. Back to the landscapes