Evolutions of architectures

This appendix details dozens of evolutions of metapatterns to show how they connect together. The evolutions probably have practical value through listing prerequisites, benefits, and drawbacks, but I am not sure that many readers will get through them without becoming bored to death. The metapattern chapters in the main parts of the book include abridged versions of the sections below.

Duplicate and similar evolutions are omitted, and I did not write any evolutions for fragmented metapatterns as you should be able to infer them on your own after having read the book. Furthermore, for some reason I don’t know of any evolutions for the implementation metapatterns, except for those that re-integrate the custom parts of the system into its core, mostly to improve the system’s performance. However, such evolutions are trivial, thus omitted.

Contents:

• 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 restructure 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 Sandwich

<< Disclaimer	^ Appendices ^	Evolutions of a Monolith that lead to Shards >>