False hope of various architectures from books
If "Hexagonal Architecture" were changed to "Hexagonal Implementation", it would be much less confusing, IMHO.
The same goes for "Vertical Slice Architecture". Do you agree that "Vertical Slice Implementation" sounds better?
Other options: โก๏ธ Approach โก๏ธ Thinking โก๏ธ Structure
๐ค Ports&Adapters Approach ๐ค Hexagonal Structure ๐ค Vertical Slice Structure โค๏ธ ๐ฉท ๐งก ๐ ๐ ๐ค Clean Thinking ๐ค Onion ๐ง Implementation ๐ค Onion ๐ง Structure
For now, for me, the Structure delivers the most meaning and what we get from those (so-called) "architectures".
Giving people hope they magically got an architecture because they implemented XYZ "ARCHITECTURE" is just cruel!
Go to the whiteboard, take a pen and design YOUR PROJECT's processes and functionalities. After that, make some bold decisions you can call Architecture.
HermesJS ๐ซ๐ฟ
But you miss a lot of things in this ecosystem. You miss a chassis.
Hermes PostgreSQL and Hermes MongoDB are part of the initiative that delivers to you a foundation of a reliable system.
It is a library, not a framework, which relies on PostgreSQL's Logical Replication / MongoDB Change Stream.
It implements the Outbox pattern. You can span a database transaction over persisting an entity and publishing a message.
Go to the docs!
Give a start on the GitHub!