Book Image

Designing Hexagonal Architecture with Java

By : Davi Vieira
Book Image

Designing Hexagonal Architecture with Java

By: Davi Vieira

Overview of this book

Hexagonal architecture enhances developers' productivity by decoupling business code from technology code, making the software more change-tolerant, and allowing it to evolve and incorporate new technologies without the need for significant refactoring. By adhering to hexagonal principles, you can structure your software in a way that reduces the effort required to understand and maintain the code. This book starts with an in-depth analysis of hexagonal architecture's building blocks, such as entities, use cases, ports, and adapters. You'll learn how to assemble business code in the Domain hexagon, create features by using ports and use cases in the Application hexagon, and make your software compatible with different technologies by employing adapters in the Framework hexagon. Moving on, you'll get your hands dirty developing a system based on a real-world scenario applying all the hexagonal architecture's building blocks. By creating a hexagonal system, you'll also understand how you can use Java modules to reinforce dependency inversion and ensure the isolation of each hexagon in the architecture. Finally, you'll get to grips with using Quarkus to turn your hexagonal application into a cloud-native system. By the end of this hexagonal architecture book, you'll be able to bring order and sanity to the development of complex and long-lasting applications.
Table of Contents (21 chapters)
1
Section 1: Architecture Fundamentals
7
Section 2: Using Hexagons to Create a Solid Foundation
12
Section 3: Becoming Cloud-Native

Assuring consistency with aggregates

We've so far seen how valuable entities are to represent things in a problem domain. Also, we saw how value objects are essential to enhance the descriptiveness of the model we are modeling. But how to proceed when we have a group of related entities and value objects that express a whole concept when put together? For such a scenario, we should employ the use of aggregates. The idea is that objects inside an aggregate operate in a consistent and isolated manner. To achieve such consistency, we must ensure that any change on any aggregate object is conditioned to the variants imposed by such an aggregate.

Aggregates are like an orchestrator that orchestrates data and behavior on the objects it controls. For this approach to work, we need to define an entry point to interact with the aggregate realm. This entry point is also known as the aggregate root, which keeps references to the entities and value objects that are part of the aggregate...