Implicit architecture
Implicit architecture is a software architecture whose significant design decisions emerge without explicit, shared, or deliberate design and governance.
Collaborative Software Design: How to facilitate domain modeling decisions
Implicit architecture is a software architecture whose significant design decisions are unstated, undocumented, or not shared.
- How it is used
- Exposes how unshared design decisions damage architecture, implementation, communication, and group dynamics.
- How deep it goes
- Explains three causes and practical consequences, while positioning collaborative modeling as a way to make decisions explicit.
- Examples
- Uses the BigScreen scenario of isolated implementation, team conflict, wrong work, delays, and rework.
- What you can do after
- Apply it via collaborative modeling to surface stakeholders’ decisions, tradeoffs, value, and architectural effects.
Microservices Patterns, Second Edition
Implicit architecture is an application architecture that emerges without anyone consciously designing or governing it.
- How it is used
- Contrasts ways of assigning architectural decisions and warns against leaving architecture without conscious thought.
- How deep it goes
- Defines implicit architecture and warns of its risk for non-trivial applications, without detailing its consequences.
- Examples
- Uses a diagram comparing four approaches to who makes architectural decisions.
- What you can do after
- Evaluate implicit architecture as a risky approach for non-trivial applications.
Read how Microservices Patterns, Second Edition explains implicit architecture →
Related concepts
- design decisionproduced by · A design decision is a deliberate choice that resolves a problem concerning a software system’s structure, behavior, implementation, or user experience.
Questions about implicit architecture
What is implicit architecture?
Implicit architecture is a software architecture whose significant design decisions emerge without explicit, shared, or deliberate design and governance.
Which Manning books explain implicit architecture?
Collaborative Software Design: How to facilitate domain modeling decisions and Microservices Patterns, Second Edition.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

