Comparison of architectural patterns
This chapter is a compilation of small sections each of which examines one aspect of the architectural patterns included in this book. It shows the value of having a list of metapatterns to iterate over and analyze.
- Sharing functionality or data among services
- Pipelines in architectural patterns
- Dependency inversion in architectural patterns
- Indirection in commands and queries
| << Analytics | ^ Analytics ^ | Sharing functionality or data among services >> |
|---|
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
