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

Using policy and specification to deal with business rules

One of the most valuable things a system possesses is its codified business rules. Those rules represent a vital effort to understand a real-world problem and translate that understanding into working software. That's not a trivial task, for sure. In DDD, we learn how crucial it is to work closely with domain experts to model our problem domain correctly. If domain experts are not available, we should seek developers with knowledge in the business. If none of them is available, we have no choice but to embark on a knowledge-seeking journey through books and any other resources that can help us grasp our problem domain's inner workings.

Once the business knowledge is acquired and we have enough relevant information about the problem domain's steps and processes, we can then start the adventure to transform that knowledge into code. At a first glance, this process to understand business needs and transform them...