You're reading from Designing Hexagonal Architecture with Java

Product type Book

Published in Jan 2022

Publisher Packt

ISBN-13 9781801816489

Pages 460 pages

Edition 1st Edition

Languages

Concepts

Software Architecture

Author (1):

Davi Vieira

Table of Contents (21) Chapters

Preface

1. Section 1: Architecture Fundamentals

2. Chapter 1: Why Hexagonal Architecture?

3. Chapter 2: Wrapping Business Rules inside Domain Hexagon

4. Chapter 3: Handling Behavior with Ports and Use Cases

5. Chapter 4: Creating Adapters to Interact with the Outside World

6. Chapter 5: Exploring the Nature of Driving and Driven Operations

7. Section 2: Using Hexagons to Create a Solid Foundation

8. Chapter 6: Building the Domain Hexagon

9. Chapter 7: Building the Application Hexagon

10. Chapter 8: Building the Framework Hexagon

11. Chapter 9: Applying Dependency Inversion with Java Modules

12. Section 3: Becoming Cloud-Native

13. Chapter 10: Adding Quarkus to a Modularized Hexagonal Application

14. Chapter 11: Leveraging CDI Beans to Manage Ports and Use Cases

15. Chapter 12: Using RESTEasy Reactive to Implement Input Adapters

16. Chapter 13: Persisting Data with Output Adapters and Hibernate Reactive

17. Chapter 14: Setting Up Dockerfile and Kubernetes Objects for Cloud Deployment

18. Chapter 15: Good Design Practices for Your Hexagonal Application

19. Assessments

20. Other Books You May Enjoy

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...