Software architecture
Software architecture is the significant structure of a software system, including its components, relationships, and design decisions that shape how the system is built and behaves.
Microservices Patterns, Second Edition
The structures of a software system, including its elements, their relationships, and their properties.
- How it is used
- Uses architecture to align system structure with fast, reliable software delivery and engineering organization needs.
- How deep it goes
- Defines architecture, examines quality attributes, and details design decisions, constraints, and their rationale.
- Examples
- Illustrates layered architecture with dependency rules and availability with a failed service instance.
- What you can do after
- Evaluate architectural choices against delivery needs, quality attributes, and the problems each decision solves.
Read how Microservices Patterns, Second Edition explains software architecture →
Grokking Software Architecture
Software architecture comprises the significant structural and behavioral decisions that shape how a software system is built, deployed, and changed.
- How it is used
- Uses architecture to turn business needs and user requirements into deliberate structural choices.
- How deep it goes
- Provides a five-stage decision process and a self-check for comparing options and recording consequences.
- Examples
- Illustrates system structure with a food truck and tradeoffs with bank transfers, social feeds, and Friendster.
- What you can do after
- Evaluate architectural choices by identifying alternatives, weighing tradeoffs, and explaining their consequences.
Read how Grokking Software Architecture explains software architecture →
Also covered in
- Claude at WorkIn early access (MEAP)
- Vanilla WebIn early access (MEAP)
- Clean Applications with Hexagonal ArchitectureIn early access (MEAP)
Related concepts
- Model–view–controllerincludes · Model–view–controller is a software architectural pattern that separates application data and behavior, presentation, and interaction handling into model, view, and controller responsibilities.
- architectural decisionhas part · An architectural decision is a significant choice about the structure, behavior, interactions, or technical constraints of a software system.
- architectural requirementconfigured by · An architectural requirement is a requirement whose fulfillment or correctness substantially influences or can change a system’s architecture.
Questions about software architecture
What is software architecture?
Software architecture is the significant structure of a software system, including its components, relationships, and design decisions that shape how the system is built and behaves.
Which Manning books explain software architecture?
Microservices Patterns, Second Edition and Grokking Software Architecture.
What is the difference between software architecture and software agility?
Software architecture is the significant structure of a software system, including its components, relationships, and design decisions that shape how the system is built and behaves. Software agility is the capacity of a software system, service, development process, or organization to adapt rapidly to changing requirements or circumstances.
What kinds of software architecture are there?
Kinds of software architecture include Model–view–controller.
What are the parts of software architecture?
Software architecture includes architectural decision and architectural relation.
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.

