Architecture
Architecture is how LEF explains and shapes systems: intent, responsibilities, boundaries, and trade-offs.
Mental models
Section titled “Mental models”C4 (structure)
Section titled “C4 (structure)”A software system is made up of one or more containers (applications and data stores), each of which contains one or more components, which in turn are implemented by one or more code elements (classes, interfaces, objects, functions, etc). And people (actors, roles, personas, named individuals, etc) use the software systems that we build. See: C4 model.
In LEF docs:
- A software system is typically an environment.
- A lane in the DTAP flow is an occurrence of that system; the construct is stable across lanes.
- Shared infra enablers (VPN/DNS/proxies/storage) are supporting systems, not “the system itself”.
System aspects (operational reality)
Section titled “System aspects (operational reality)”We use an aspect model to describe systems as operational realities: not just “what runs”, but also how it is built, released, secured, and operated.
Each aspect is described through three dimensions: organization, process, and technique.
Explore: Aspects.
Terms: lane · DTAP · aspect model
Start here
Section titled “Start here”Views (how to navigate)
Section titled “Views (how to navigate)”| View | Purpose | LEF docs entry point |
|---|---|---|
| System context | Big picture: system boundary, people, and external dependencies. | System archetypes |
| Container model | Major runtime building blocks (apps + data stores). | System archetypes |
| Container archetypes | The canonical container types inside systems. | Container archetypes |
| Infra enablers | Shared infra capabilities used by many systems. | Infra enablers |
| Deployment (lanes) | Where instances live and how shared enablers fit per lane. | Delivery aspect |
Boundaries (where things live)
Section titled “Boundaries (where things live)”- Architecture: explanation + maps + rationale (no inventories, no runbooks).
- Reference: canonical facts (domains, servers, databases, environment definitions).
- Run & Support: procedures, troubleshooting, and operational checklists.