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

Modeling a problem domain with entities

In DDD, before any code is written, there must be lots of discussions between developers and domain experts—the people who have a deep understanding of the business. Those discussions provide valuable information acquired through a process called knowledge crunching, which is based on brainstorming between those developers and domain experts. That knowledge is then incorporated into the Ubiquitous Language. This language works as the lingua franca among everyone involved in the project and is present in documentation, day-to-day conversations, and—of course—in the code.

When we're dealing with entities, we must always pay attention to how much we can learn about the business by just reading the code, because the real deal happens when we employ the knowledge-crunching technique in order to continually evolve the Ubiquitous Language and make the code speak that language. That's the basis for rich entities that...