Hexagonal Architecture Explained: How the Ports & Adapters Architecture Simplifies Your Life, and How to Implement It (Series on Object-Oriented Design)
Description
"Looking at the screen of my laptop, I realized that it was full of code that didn't let me understand what it did regarding business logic. From that moment I began to search until I discovered the architecture that decouples the business logic from the frameworks: Hexagonal Architecture, more correctly called Ports & Adapters. From that moment until now, I haven't stopped reading and learning about this pattern."
Recommended by giants like Netflix and Amazon, the Hexagonal or Ports & Adapters architecture simplifies testing, protects against business logic leakage, supports changing technologies in long-running system, and lets you apply Domain Driven Design. In this definitive book on the subject, pattern author Dr. Alistair Cockburn and Juan Manuel Garrido de Paz lay bare all of the intricacies of the pattern, providing sample code and answering your many frequently asked questions.
More details
Content
- Intro
- Preface
- Chapter 1: Introduction
- 1.1. Copy this code
- 1.2. Short history of the pattern
- 1.3. Why the name "Hexagonal" Architecture?
- 1.4. The costs and benefits of this pattern
- Chapter 2: Ports & Adapters Defined
- 2.1. Glossary
- 2.2. The pattern elements: App, Ports, Actors, Adapters
- 2.3. The 5th element: The Configurator
- 2.4. What is required, optional, and outside the pattern
- Chapter 3: Code Samples
- 3.1. The simplest example: the tax calculator
- 3.2. Another simple example, the web-hexagon
- 3.3. The BlueZone example
- Chapter 4: FAQ - What and How?
- 4.1. The dinner boat analogy
- 4.2. The hardware chip analogy
- 4.3. What is a port?
- 4.4. Where do I put the "app" boundary?
- 4.5. How many ports should I have?
- 4.6. How do I structure the inside of my app?
- 4.7. How do I structure my adapters?
- 4.8. Where do I put my files?
- 4.9. What is the development sequence?
- Chapter 5: FAQ - Related Concepts
- 5.1. How does this relate to use cases?
- 5.2. How does this relate to Walking Skeleton?
- 5.3. Is the pattern symmetric or asymmetric?
- 5.4. Is the test suite a driving actor or an adapter?
- 5.5. Layered, onion, clean, hexagonal: what is the difference?
- 5.6. How does this relate to DDD?
- 5.7. DDD's anti-corruption layers
- 5.8. What about nested hexagons?
- 5.9. Is CQRS an example of Ports & Adapters?
- Chapter 6: The Original Articles
- 6.1. The longer history
- Reflections on the history
- 6.2. The original article: The Hexagonal (Ports & Adapters) Architecture
- 6.3. Comments on the original article in 2023
- 6.4. The article: "Component + Strategy generalizes Ports & Adapters
- 6.5. The article: "Configurable Receiver
- Chapter 7: Summary
- 7.1. The pattern in its shortest form
- 7.2. The sample code to copy
- 7.3. The costs and benefits of this pattern
- 7.4. Why the name "Hexagonal" Architecture?
- Fin
