LADRs to formalize architecture and design decisions in distributed / autonomous development
We are often left to address the gaps from architectural principles (which stay at a pretty high and abstract level) to the actual implementation detail. Here is an attempt to bridge that gap by providing a set of Lightweight Architecture Decision Records (LADRs) which are simple to follow and can be implemented in a given team/project by the developers
Lightweight architecture decisions records support aligned autonomy in design
Status
-
Proposed -
Trialing -
Under review -
Approved -
Retired
Context
We need a mechanism to support agile decision making in an open source, distributed development project.
Scope
- Decisions affecting OSDU behavior
- Decisions affecting the boundaries between common code and cloud infrastructure
Decision
We will adopt lightweight architecture decision records as a mechanism to develop, review and communicate design decisions in OSDU.
Rationale
Balancing agility in design / architecture with scalability in roll-out.
Consequences
Without a formalized approach we either end up with chaos or paralysis.
When to revisit
When the PMC structure is in place.