I'm pushing the information into open-source (CC-BY license) with the hope to get community support. If that happens, people will tell me of new and missing patterns - or even add them to the book without my help. That way the book may remain up to date - but only if it makes enough noise to become widely known.

There is a trouble with novel patterns - they are poorly defined - or even the same term is used in multiple ways. For example, I've read of Nanoservices as:

1) auto-generated pipeline of lambdas (which I used),

2) a lambda per API method (in Building Serverless Web Applications),

3) fine-graned modular monolith.

In the same way there are at least 2 definitions for Cells (WSO2 and Amazon) - I had to mention both in the book.

>> "study domains beneath your home domain" - I reinvented Hexagonal Architecture while working on a low-end (4KB RAM) DECT system. It was an actor-based legacy when there came a new standard which used system-wide state in multiple scenarios. As you know, it's hard to get a consistent state snapshot for an asynchronous system. Merging all the business logic together while leaving the periphery asynchronous resolved the issue. But Hexagonal Architecture is backend which is no way below embedded telecom.

Thus, in my experience, domain-dedicated patterns represent specific views of the general principles of architecture, and it is this principles that I hope to expose by collecting similar patterns from various domains and times.