The book is a compendium of architectural patterns which sorts them out into a tree-like hierarchy based on the pattern's structure and function. This allows for grouping hundreds of patterns into less then 20 classes and exploring the common features, applicability, and performance of each class.

It also includes supplementary topics that range from the discussion on the nature of complexity to the comparison of orchestration, choreography, and integration through shared data. Aside of that, there is a wide range of evolutions which show how a system may change under different forces.

The book is AI-free, 440 pages long, and includes hundreds of box-and-arrow diagrams. It can be downloaded from:

- GitHub https://github.com/denyspoltorak/metapatterns

- Leanpub https://leanpub.com/metapatterns

- or read online (the dark theme is supported) https://metapatterns.io/

Thank you for sharing!

The series of articles investigates the way structures of asynchronous systems influence their properties.

The article draws structural diagrams for advanced architectural patterns, namely:

* Hexagonal Architecture, Gateway, Application Service;

* Middleware, Shared Repository, Plug-ins;

* Microkernel, Domain-Specific Language, Orchestrators.

It investigates how pattern structures define their properties and draws relations between architectures.

Gotcha! MVC is a kind of Hexagonal Architecture.

Bonus: (Re)Actor-with-Extractors that toggles between the shared memory and actor paradigms.

The article covers basic architectural patterns, namely

-- Shards/Instances

-- Layers

-- Services: Microservices, Pipeline, Nanoservices

their benefits, drawbacks and relations to more complex architectures.

A comparison of architectural patterns for handling messages:

-- Reactor (imperative programming with blocking calls),

-- Proactor (reactive programming with non-blocking calls),

-- Half-Sync/Half-Async (imperative logic over a reactive framework).