Download as PDF, PPTX
Uploaded byComsysto Reply GmbH
ljug-meetup-2023-03-hexagonal-architecture.pdf
The document discusses the evolution and principles of hexagonal architecture, also known as ports and adapters architecture, as introduced by Alistair Cockburn and elaborated by others like Jeffrey Palermo and Robert C. Martin. It emphasizes the importance of separating concerns for better testability and adaptability while outlining the roles of various architectures like onion, clean, and microservices within the context of domain-driven design. Key recommendations include focusing on domain objects and isolating technologies to enhance understanding and maintainability.
More Related Content
Similar to ljug-meetup-2023-03-hexagonal-architecture.pdf
ljug-meetup-2023-03-hexagonal-architecture.pdf
- 1. ANATOMIE EINER HEXAGONALEN ARCHITEKTUR Lightweight JavaUser Group München 20. März 2023
- 2. OTTO Solutions Architect @Comsysto Reply SVEN Solutions Architect @ Comsysto Reply
- 3. A little bitof history …
- 4. Hexagonal Architecture 2005 Alistair Cockburn “Ports &Adapters Architecture” - Separation of Concerns - (UI & DB) Testability & Mockability - “Primary/Secondary” or “Driving/Driven” Adapters - Use Cases as Application Boundary https://alistair.cockburn.us/hexagonal-architecture/
- 5. Onion Architecture 2008 Jeffrey Palermo - Separationof Concerns via Controlled Coupling - Application Core: Object Model (Domain Model) with Business Rules - Externalize Infrastructure - Relies on Dependency Inversion https://jeffreypalermo.com/2008/07/the-onion-architecture-part-1/
- 6. Clean Architecture 2012 Robert C. Martin -The Dependency Rule - Entities encapsulate Business Rules - Use Cases as Layer - What and how to cross boundaries: Flow - Different wording, similar concepts https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html
- 7. Enter the Microservice Hype 2012+ -Microservices - Domain-Driven Design (DDD) - CQRS - … - We need to talk! DDD, Hexagonal, Onion, Clean, CQRS, … How I put it all together
- 8. Let’s start withthe essentials …
- 9. There is one essentialthing … … there is the inside and the outside … Alistair Cockburn Dennis Hamilton - https://www.flickr.com/photos/orcmid/1850093537/
- 10. There is one essentialthing … .. and it needs to be connected …
- 11. Why should Icare?
- 12. Separate Technologies Does this lookfamiliar?
- 13. Does this lookfamiliar? Separate Technologies
- 14.
- 15. Okay, what doI have to do?
- 16.
- 17. … and aHexagonal Architecture …
- 18. It’s a Questionof Ownership In a layered architecture …
- 19. It’s a Questionof Ownership In a hexagonal architecture …
- 20. It’s a Questionof Dependency
- 21. It’s a Questionof Dependency
- 22.
- 23.
- 24.
- 25. There is another thing… … but it is often not so important to differentiate …
- 26. Things to noteabout ports …
- 27. Incoming vs. Outgoing Ports …the same goes for adapters …
- 28. Incoming Ports … areoften use case centric …
- 29. Outgoing Ports … areoften domain object centric …
- 30. What is mydomain?
- 31. What is mydomain anyway? https://github.com/ddd-crew/core-domain-charts
- 32.
- 33. - Think domainfirst - Use the domain objects in the ports if possible - Isolate technologies in the adapters - Move business logic as far to the center as possible It’s not so complicated
- 34. - Better testability -Easier to understand - Easier to adapt to technological changes - Easier to guard against regressions - Easier to focus on business code And the benefits are …
- 35.