Book Image

Designing Hexagonal Architecture with Java - Second Edition

By : Davi Vieira
Book Image

Designing Hexagonal Architecture with Java - Second Edition

By: Davi Vieira

Overview of this book

We live in a fast-evolving world with new technologies emerging every day, where enterprises are constantly changing in an unending quest to be more profitable. So, the question arises — how to develop software capable of handling a high level of unpredictability. With this question in mind, this book explores how the hexagonal architecture can help build robust, change-tolerable, maintainable, and cloud-native applications that can meet the needs of enterprises seeking to increase their profits while dealing with uncertainties. This book starts by uncovering the secrets of the 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 with ports and use cases in the application hexagon, and make your software compatible with different technologies by employing adapters in the framework hexagon. In this new edition, you’ll learn about the differences between a hexagonal and layered architecture and how to apply SOLID principles while developing a hexagonal system based on a real-world scenario. Finally, you’ll get to grips with using Quarkus to turn your hexagonal application into a cloud-native system. By the end of this book, you’ll be able to develop robust, flexible, and maintainable systems that will stand the test of time.
Table of Contents (24 chapters)
1
Part 1: Architecture Fundamentals
7
Part 2: Using Hexagons to Create a Solid Foundation
12
Part 3: Becoming Cloud-Native
18
Part 4: Hexagonal Architecture and Beyond

Understanding the problem domain

We will start modeling the problem domain by considering the fact that a core router can connect to both core and edge routers. Edge routers, in turn, connect to switches and their networks. The following diagram depicts this scenario:

Figure 6.2 – A use case for the topology and inventory network system

Figure 6.2 – A use case for the topology and inventory network system

Core routers are faster and deal with high traffic loads, and they don’t deal directly with the traffic generated from a switch and its networks. Conversely, edge routers deal directly with traffic generated by a switch and its networks. In our scenario, an edge router is not allowed to connect to other edge routers; it can only connect to core routers and switches. A switch can have multiple networks.

Bear in mind that’s a particular arrangement established for our scenario. By no means does it represent a strict rule of how to organize network components. Here is a diagram showing the arrangement...