Marcos Fernández

Hexagonal Architecture might be proposed to solve the problems back in the days. But that is completely unnecessary and I would even say overkill for most of the applications. All the driver side, driven side, port, adapter, etc is just more buzzwords describing decoupling the implementation using programming-to-interfaces technique. Nothing more, nothing less. I took one of the Hexagonal Architecture implementation of a Spring Boot app github.com/sivaprasadreddy/h… Created the same application using simple layered architecture (layered-app module) and yet achieve the goals: * Separation of the concerns ✅ * Testability ✅ * Less code, more readable & to the point 🎯 * No unnecessary interfaces with only one implementation 🚫 * No InMemory implementations just for satisfying imaginary testing/local_dev requirements. Use Testcontainers to test with what actual DB you use in production. 🚫 * Made the Service layer as transactional boundary as it should be. ☑️ Stop cargo-cult programming.