The heart of software architecture
As the visible world boils down to protons and neutrons which stick together in various combinations, so too does the entirety of software architecture as a field of endeavor grow from an interplay of cohesion and decoupling.
| << Real-world inspirations for architectural patterns | ^ Analytics ^ | Cohesers and decouplers >> |
|---|
Analytics
Appendices
- Acknowledgements
- Books referenced
- Copyright
- Disclaimer
-
Evolutions of architectures
- Evolutions of a Monolith that lead to Shards
- Evolutions of a Monolith that result in Layers
- Evolutions of a Monolith that make Services
- Evolutions of a Monolith that rely on Plugins
- Evolutions of Shards that share data
- Evolutions of Shards that share logic
- Evolutions of Layers that make more layers
- Evolutions of Layers that help large projects
- Evolutions of Layers to improve performance
- Evolutions of Layers to gain flexibility
- Evolutions of Services that add or remove services
- Evolutions of Services that add layers
- Evolutions of a Pipeline
- Evolutions of a Middleware
- Evolutions of a Shared Repository
- Evolutions of a Proxy
- Evolutions of an Orchestrator
- Evolutions of a Combined Component
- Format of a metapattern
- Glossary
- History of changes
- Index of patterns
- Martin Fowler's Bliki
- Software Architecture Chronicles
- Enterprise Integration Patterns
- Microservices Patterns
- Gang of Four Design Patterns
- Game Programming Patterns
- PLoP Archive
- Metapatterns website
