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

The need to create ports and use cases

After putting some effort into modeling the problem domain in the Domain hexagon, the next step is to move on to the Application hexagon and define how the software system enables the behavior that fulfills the business-related operations that come from the Domain hexagon. Actors—who could be both users and other systems—drive these behaviors. They dictate the system's capabilities.

The moment when we start implementing the Application hexagon is crucial because we begin to think in aspects that are not directly related to the domain model. Instead, these aspects may be related to integrations for communicating with other systems. But we shouldn't go so far as to decide which technologies to use. We don't take decisions related to technology when implementing the Application hexagon. Rather, technology concerns are a subject that we go deep into in the Framework hexagon.

We employ use cases to define what a system...