Architecture Atlassoftware · systems · evidence
Software · Systems · Quality · EvolutionView Markdown source

Evolutionary architecture, governance, platform, and organization

Architecture is a living capability. Evolutionary architecture supports guided incremental change through fitness functions, reversible decisions, observability, and governance close to delivery.

Core ideas and patterns

Idea What it solves Cost, limit, or warning
Conway's law Connects communication structures to system structure Reorg charts alone do not create good boundaries
Inverse Conway maneuver Shapes teams to encourage desired architecture Forced boundaries without domain fit create coordination
Team Topologies Clarifies stream-aligned, platform, enabling, and subsystem interactions Labels without cognitive-load reduction add little
Paved road Provides a supported secure delivery path A mandatory road that ignores users becomes a blockade
Architecture runway Builds enabling capability ahead of near-term demand Too much runway becomes speculative platform work
Fitness function Guards important qualities continuously Needs business-aligned thresholds
Architecture guild Shares practice without centralized command Advice needs accountable owners and adoption evidence
Standard/exception process Balances reuse with justified variation Slow exceptions drive shadow architecture
Deprecation/retirement Removes obsolete contracts and technology safely Inventory and consumer evidence are prerequisites

How to apply it

Assign clear decision rights. Keep organization-wide principles few and enforceable. Provide golden paths, reference implementations, self-service platforms, and automated controls. Allow time-bound exceptions with risk owner and exit plan. Review portfolios for duplication, obsolete dependencies, and systemic concentration risk.

Evidence, not opinion

Measure platform adoption and satisfaction, cognitive load, lead time, change failure, dependency age, exception duration, architecture-test pass rate, service ownership, and retirement progress.

Small example

A platform offers identity, service templates, telemetry, delivery, and secrets as self-service. A team may deviate for a proven need, but owns extra operations and records a review trigger.

Feynman check

Explain the design to a new engineer without using the pattern names. State the problem, the forces that conflict, the chosen boundary or mechanism, what can fail, and the evidence that would prove the choice still works.

Architecture AtlasIndependent study material · verify standards at their primary sources