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

Introducing JPMS

Before Java SE 9, the only mechanism we had to handle dependencies in Java was the classpath parameter. The classpath parameter is where we put dependencies in the form of JAR files. However, the problem is that there is no way to determine which JAR file a particular dependency came from. If you have two classes with the same name, in the same package, and present in two different JAR files, one of the JAR files would be loaded first, causing one JAR file to be shadowed by the other.

Shadowing is the term we use to refer to a situation where two or more JAR files that contain the same dependency are put into the classpath parameter, but only one of the JAR files is loaded, shadowing the rest. This JAR dependency entanglement issue is also known as JAR hell. A symptom that indicates that things are not so good with dependencies that have been loaded into the classpath parameter is when we see unexpected ClassNotFoundException exceptions at system runtime.

JPMS...