This project is used to show how the hexagonal architecture can be applied to a Microservice (Spring Boot) and a native binary AWS Lambda (Quarkus) in a multi module project. However, I'm not aware of a 'standard' project structure for JVM microservices so this is my interpretation of how to design and implement a hexagonal architecture for the JVM. Personally I've used hexagonal architectures with DDD for years because it aligns well with how I reason about designing applications. The application has a semantically sound interaction with the adapters on all sides of it, without actually knowing the nature of the things on the other side of the adapters.” When the application has something to send out, it sends it out through a port to an adapter, which creates the appropriate signals needed by the receiving technology (human or automated). The application is blissfully ignorant of the nature of the input device. Hexagonal Architecture (aka Ports and Adapters) / Clean Architecture / DDDĪllow an application to equally be driven by users, programs, automated test or batch scripts, and to be developed and tested in isolation from its eventual run-time devices and databases.Īs events arrive from the outside world at a port, a technology-specific adapter converts it into a usable procedure call or message and passes it to the application.

Internal modifier in kotlin