What do you get with eBook?

Instant access to your Digital eBook purchase

Download this book in EPUB and PDF formats

Access this title in our online reader with advanced features

DRM FREE - Read whenever, wherever and however you want

AI Assistant (beta) to help accelerate your learning

Key benefits

Learn techniques to decouple business and technology code in an application

Apply hexagonal architecture principles to produce more organized, coherent, and maintainable software

Minimize technical debts and tackle complexities derived from multiple teams dealing with the same code base

Description

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.

Who is this book for?

This book is for software architects and Java developers who want to improve code maintainability and enhance productivity with an architecture that allows changes in technology without compromising business logic, which is precisely what hexagonal architecture does. Intermediate knowledge of the Java programming language and familiarity with Jakarta EE will help you to get the most out of this book.

What you will learn

Find out how to assemble business rules algorithms using the specification design pattern

Combine domain-driven design techniques with hexagonal principles to create powerful domain models

Employ adapters to make the system support different protocols such as REST, gRPC, and WebSocket

Create a module and package structure based on hexagonal principles

Use Java modules to enforce dependency inversion and ensure isolation between software components

Implement Quarkus DI to manage the life cycle of input and output ports

What do you get with eBook?

Instant access to your Digital eBook purchase

Download this book in EPUB and PDF formats

Access this title in our online reader with advanced features

DRM FREE - Read whenever, wherever and however you want

AI Assistant (beta) to help accelerate your learning

Frequently bought together

Hands-On Software Architecture with Java

€41.99

Designing Hexagonal Architecture with Java

€35.99

Domain-Driven Design with Java - A Practitioner's Guide

€31.99

Total € 109.97

Fernando Jan 10, 2022

Great book for Java Developer's and Architects entering in a way of architecting software decoupling business from technological area using Hexagonal.This book contains enumerated step-by-step explanations accompanied with practical examples. Very well written in an easy to grasp manner.I particularly like the focus across Quarkus that I particullary not familiar with, that show us how to implement dependency injection using Quarkus DI approach for instance.

Amazon Verified review

Aleksandr Teterin Jan 10, 2022

I read the book as I was really interested in finding Hexagonal Architecture's implementation. I know only a few books dedicated to the topic, and I am glad to read one more - especially one that uses Java, Quarkus as an implementation platform.If you are wondering how to build a medium or large application, that:is having the complex business domain, and alsogoing to have a long life in production, and alsoshould be adaptable to the future changes of requirementsThen eventually, you will find out that hexagonal architecture could be an option that might help you achieve the above goals.I am finding the book well balanced in terms of theory and practice. It looks more practical (and I like it), and in terms of theory, the author provided enough supporting references.Also, there are questions/answers for the self-check that help the readers understand if they are on the right track.The source code accompanies all chapters. If some of the author's ideas were new for me, then after the building and running the application from the source code, I addressed all my questions.Application testing. The book covers the unit, BDD, and integration testing of an application.I also want to mention some limitations/neutral comments. You need to keep in mind that provided implementation options might not work for you.To be more specific. In chapter 5 the implementation of the addNetworkToRouter use case contains the calls to Kafka and to a database. In real life, the Kafka call may fail for any reason (server is down, network issue) while the database is available. In that case, the valuable user input will be lost. Another comment is about using reactive implementation. Readers may conclude that the reactive approach is the default one as it has a better performance than the imperative approach. While it is true, but if your application is not affected by C10k problem (you are not building the Netflix) then probably you want to prefer the imperative approach. Why? I would refer the readers to Tomasz Nurkiewicz's "Reactive programming lessons learned" talk for a detailed explanation.In the end, I want to say that I enjoyed the journey about building Hexagonal Architecture from scratch. I intend to use the book as a reference in my future projects.

Amazon Verified review

Kelvin D. Meeks Mar 22, 2022

If I had to pick just two words to describe this excellent book on Hexagonal Architecture with Java – it would be “Depth & Detail”.What I particularly liked:The writing is crisp and succinct.A detailed coverage of all aspects of Hexagonal Architecture considerations.Good weaving of the foundational principles and concepts of Hexagonal Architecture (that originated with Alistair Cockburn – with additional contributions from others, over time).The obvious care and attention that the author has given in considering the many concerns and dimensions of teaching and illustrating Hexagonal Architecture concepts.The inclusion of a “Summary”, Questions”, and sometimes a “Further Reading” section - at the end of the chapters.The careful and meticulous layering of information, from chapter to chapter – slowly building up a conceptual model in the reader’s mind – backed by the numerous concrete , non-trivial, hands-on examples, with illustrative code.The complete treatment from a real-world engineering perspective – from design to development, testing, and deployment. The author leverages numerous libraries and tools (Swagger, RESTEasy, Quarkus, JPMS, Hibernate Reactive, Panache, MySQL, Vert.x, Docker, Kubernetes)– beyond just the Java language – weaving some important concepts and techniques (Business Model Canvas, Lean Canvas, Event Storming, Domain Driven Design, Bounded Context, Behavior-Driven Development, CI/CD, OpenAPI, REST APIs, Use Cases, Dependency Inversion, CDI Beans, ORM, Cloud Deployment) – that will elevate the skills and expertise less experienced developers.This book is very suitable for software engineers, system architects, solution architects, and enterprise architects – that have an interest in learning about Hexagonal Architecture. It is also quite readable by less technical IT folks.

Amazon Verified review

Mark Richards Feb 01, 2022

I thought this book did a good job of describing the connection between an architectural style and how it impacts the structure and design of the corresponding code. The book is well-written, and is also very well organized in a clear and methodical approach. The book starts out with a good explanation of hexagonal architecture and the various parts of the architecture style, and then takes the reader through each of the main parts of hexagonal architecture structure (domain, application, framework) through implementation examples using Java. I thought the use of the network cataloging system example was a fresh relief from other more "traditional" examples, and was detailed and interesting enough to keep my attention throughout the book.Writing an architectural implementation book is challenging due to the (literally) hundreds of technical implementation possibilities that exist. In this case the author chose to use Java combined with Maven, Cucumber, curl, Postman, Newman, Kafka, JPMS, Quarkus, JPA, Hibernate, RESTEasy Reactive, OpenAPI, Swagger, Docker, and Minikube. While that's a lot of frameworks and tools to install and learn, what you end up with at the end of a book is a complete end-to-end executable example implemented using hexagonal architecture. Don't worry through - the author did a good job of walking through the configuration for each of these tools and frameworks for those not familiar with them, and allowed the reader to gain some exposure to these common artifacts. That said, I would have preferred to work with a simpler tech stack so that the focus was more on the architecture style rather than the myriad of tools and frameworks needed to develop and run the sample application. That said, I'm not really sure such a thing exists today given the complex tech stacks we all have to deal with to develop the simplest of applications.Having read through the whole book, I have two main observations. The first is that the book seemed more about programming techniques for creating an end-to-end complete application in the Java platform rather than focusing on the specific nuances associated with the hexagonal architecture style. While the author did a good job of tying back the separation of concerns (and corresponding code) between domain objects, ports, and adapters, I felt at times I got way too caught up in the weeds of technology and implementation details. Rather, I would have enjoyed a comparison of what certain parts would look like if they were implemented in, say, a traditional n-tiered layered architecture, and how the code structure would vary.My second observation is that I felt the author could have spent more time talking about the disadvantages and tradeoffs associated with the hexagonal architecture style. In the summary the author did mention that hexagonal architecture isn't for everyone, but I would have loved a deeper dive into what some of those tradeoffs and disadvantages are. Overall, I would say a worthwhile read for those in the Java platform.

Amazon Verified review

Priya R Shastri Jan 07, 2022

This book is an architect’s guide to writing change tolerant applications eith Java programs and Quarkus. This book has 15 chapters with each chapter having a well defined focus area. This book is for architects who want to enhance the code maintainability and availability over a long period of time.In chapter 1 the author talks about hexagonal architecture and its advantages and disadvantages. You will learn a lot about domain availability, ports and adapters. Domain Driven Design (DDD) is explained in this architecture where the design of the software is not important for the architect or the developer but for all the people involved in the design of the software in the domain. Hexagonal architecture means that the software should work independently without the database or an UI and one should be able to write software tests on those objects alone.Separating business code from technology code is the underlying idea of hexagonal architecture. The Domain, Framework and the Application are 3 hexagons that are present in the system(see diagram below)In chapter 2 Wrapping business rules inside domain hexagon, the author further describes the DDD and why there should be a difference between the technology and the application hexagon code. Business rules and business data constitute the entity portion of the domain hexagon.Aggregate grouping together of all network components. In chapter 3 Ports and user cases are discussed inside the Application hexagon. Use cases consists of UML diagrams with actors, process and outputs. In chapter 4 the author describes creating adapters for communicating with the external world. The CLI input adapter is discussed. In chapter 5 the author describes the driven and the driving operations for the applications. Working of applications with messaging systems like Kafka are discussed in here. In chapter 6 the details of building the domain hexagon is discussed. In chapter 7, building the application hexagon is discussed using Maven. The @NetworkAdd @NetworkRemove @ NetworkCreate interfaces are discussed here. The Domain hexagon is the bottom layer, the application hexagon goes on top. In chapter 8 building the framework hexagon is discussed. Chapters 10 -15 help in understanding how the applications can become cloud native aware.Overall,great material for learning the organization of coding patterns and the design patterns in Java.Good reference material. The code is provided as a link which can be downloaded.I would recommend this book as a new paradigm in architecture design in programming.

Amazon Verified review

Designing Hexagonal Architecture with Java: An architect's guide to building maintainable and change-tolerant applications with Java and Quarkus

What do you get with eBook?