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

Expressing software behavior with use cases

A software system is nothing more than a set of behaviors working together to achieve the goals defined by users or even other software systems. A software behavior, in turn, is a worthy action that, alone or combined with other software actions, contributes to realizing a worthy software goal. Such goals are intimately connected to the desires expressed by interested users or systems.

We can classify those interested folks as stakeholders or actors from which we will ultimately derive the real-world needs that will be transmuted into goals. These actors' goals will be fulfilled by the System under Discussion (SuD), or simply the software you are developing.

From the hexagonal architecture’s standpoint, we can relate these actors to what we saw in Chapter 1, Why Hexagonal Architecture?, when discussing driver and driven operations. In the same vein, we can classify the SuD actors: the driver actor is a person or system that...