SmartOrder — Part 2: The Services Layer Architecture

In the previous article, I introduced SmartOrder as a modern microservices reference platform designed around DDD, REST + HATEOAS, OpenAPI, AsyncAPI, and event-driven principles . In this article, we focus exclusively on the services layer structure of the repository: 👉 https://github.com/portus84/smartorder-ms/tree/develop/services This is not a deep dive into individual services — those will be covered in dedicated articles. Instead, this post explains the architectural blueprint behind the services module and why it is structured this way. Why a Single services Aggregator Module? Unlike many microservices repositories that split each service into completely separate repositories, SmartOrder adopts a single multi-module Maven structure . This decision was intentional and driven by: Blueprint visibility Consistent dependency management Architectural governance Easier local development Clear separation between shared infrastructure and business services The services directory acts as a