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.

Artur Wojnar

Stuck on a hard technical decision?

Book a short call and let's talk about where you're stuck.

Book a call >>
🇬🇧 EN
🫒

HermesJS 🫒🌿

Reliable messaging for Node.js / TypeScript. Hermes PostgreSQL (logical replication) & Hermes MongoDB (change streams) implement the Outbox pattern — span a DB transaction over persisting an entity and publishing a message. A library, not a framework.

Docs >>