This is an excerpt from The Art of Agile Development, Second Edition. Visit the Second Edition home page for additional excerpts and more!
This excerpt is copyright 2007, 2021 by James Shore and Shane Warden. Although you are welcome to share this link, do not distribute or republish the content without James Shore’s express written permission.
Evolutionary System Architecture
- Programmers, Operations
We build our infrastructure for what we need today, without sacrificing tomorrow.
- Simple Design
- Incremental Design
- Reflective Design
Simplicity is at the heart of Agile, as discussed in the “Key Idea: Simplicity” sidebar. It’s particularly apparent in the way fluent Delivering teams approach evolutionary design: they start with the simplest possible design, layer on more capabilities using incremental design, and constantly refine and improve their code using reflective design.
What about your system architecture? By system architecture, I mean the components that make up your deployed system. The applications and services built by your team and the way they interact. Your network gateways and load balancers. Even third-party services. What about them? Can you start simple and evolve from there?
That’s evolutionary system architecture, and I’ve seen it work on small systems. But system architectures are slow to evolve, so there isn’t the same depth of industry experience behind evolutionary system architecture that there is behind evolutionary design. Use your own judgment about how and when it should be applied.
I make a distinction between system architecture and application architecture. Application architecture is the design of your code, including decisions about how to call other components in your system. It’s discussed in the “Application Architecture” section. This practice discusses system architecture: decisions about which components to create and use, and the high-level relationships between them.
...to continue reading, buy the book!
In this Section
- Evolutionary System Architecture
- Are You Really Gonna Need It?
- Aim for Simplicity
- 1. Start with an ideal world
- 2. Introduce imperfect components and networks
- 3. Limit resources
- 4. Consider humans and teams
- Controlling Complexity
- Evolutionary design
- Fast deployment
- Vertical scaling
- Refactoring System Architecture
- Multirepo components → Monorepo components
- Components → Microliths
- Microliths → Modules
- Modules → New modules
- Big ball of mud → Modules
- Modules → Microliths
- Microliths → Components
- Modules → Components
- Monorepo components → Multirepo components
- Compound refactorings
- Alternatives and Experiments
- Further Reading