Download as PDF, PPTX
![See more…
• RESTful API with Spring Boot
• Securing REST APIs
• References:
[1] alistair.cockburn.us/Hexagonal+architecture
[2] www.infoq.com/news/2013/08/hexagonal-lifepreserver-spring
[3] github.com/russmiles/life-preserver-introductory-article-developer-magazine/
blob/master/README.md
[4] github.com/spring-guides/deprecate-tut-rest
[5] blog.ploeh.dk/2013/12/03/layers-onions-ports-adapters-its-all-the-same
/ fabricioepa.wordpress.com](https://image.slidesharecdn.com/javadev-hexagonalarchitectureforjavaapplications-150202062634-conversion-gate01/85/Hexagonal-architecture-for-java-applications-28-320.jpg)
![See more…
• RESTful API with Spring Boot
• Securing REST APIs
• References:
[1] alistair.cockburn.us/Hexagonal+architecture
[2] www.infoq.com/news/2013/08/hexagonal-lifepreserver-spring
[3] github.com/russmiles/life-preserver-introductory-article-developer-magazine/
blob/master/README.md
[4] github.com/spring-guides/deprecate-tut-rest
[5] blog.ploeh.dk/2013/12/03/layers-onions-ports-adapters-its-all-the-same
/ fabricioepa.wordpress.com](https://image.slidesharecdn.com/javadev-hexagonalarchitectureforjavaapplications-150202062634-conversion-gate01/75/Hexagonal-architecture-for-java-applications-28-2048.jpg)
Uploaded byFabricio Epaminondas
Hexagonal architecture for java applications
The document discusses hexagonal architecture, also known as ports and adapters architecture. It is an alternative to traditional multi-layer architectures that aims to decouple the application core from external influences like databases, web frameworks, and other dependencies. The core domain logic is separated from external influences by defining application programming interfaces (APIs) called "ports" that external "adapters" implement. This allows the core to be developed and tested in isolation. The document provides an example implementation of a ticket management system using this architecture.
More Related Content
Similar to Hexagonal architecture for java applications
Hexagonal architecture for java applications
- 1. Java Development HEXAGONAL ARCHITECTURE for JavaApplications
- 2.
- 3. 01 What drivesthe software architecture? • High Maintainability • Low Technical Debt: The cost payed by bad decisions • Lack of understanding • Lack of tests • Lack of documentation • Lack of collaboration • Lack of process
- 4. 01 Common multi-layerarchitecture ! " # " ! UI Layer " Application Layer # Data " Crosscutting Dependency
- 5. 01 Multi-tier architecture WebApplication Tier ! ! " " " # # # " " " ! " Client Tier Browsers, Frontend App Mobile devices, PC$Q % ! + Data / Integration Tier Database, File Storage, External Systems, Cloud & ERP CRM DOCs Dependency
- 6. 01 Dependency inversionprinciple Reference: http://blog.ploeh.dk/2013/12/03/layers-onions-ports-adapters-its-all-the-same Dependency DANGER - Possible business logic leaks
- 7.
- 8. 02 Intent • Alternativenames • Ports & Adapters • Onion Architecture / Onion Layers “Allow an application to equally be driven by users, programs, automated test or batch scripts, and to be developed and tested in isolation from its eventual run- time devices and databases.” Alistair Cockburn
- 9. 02 Key Concepts Portsare interfaces Adapters are implementations
- 10. The big picture:Ports & Adapters02 "Application Port Port Port Mock DB DB Integration Test Agent UI Adapter Adapter Adapter Adapter Use Case Boundary ‘’driven’’ adapters ‘’driver’’ adapters
- 11. Overview02 In-Memory "Application # Database ( WebServices ) ) Enterprise Integration * SQL Server REST Adapter * Configuration + Test Agent ! HTML5 App Environment Adapter File Source Adapter , SQL Adapter # NoSQL Adapter - MQ Service MQ Adapter . . Messaging Queue &ERP CRM DOCs EI Adapter (SOAP Adapter TEST Adapter
- 12.
- 13. 03 • Organizing Concernsand Code with Domains • Well defined boundaries between domains • Simple event-driven components • Life Preserver diagram Life preserver approach by Russ Miles
- 14. Life Preserver diagram03 Integration Core DomainEvent Service Domain Boundary
- 15. Notes03 • Core • Singlepurpose • Focus on unit testing • No side-effects • Integration • Side effects
- 16.
- 17. Kick-off04 github.com/fabricioepa/lab- springboot-rest-sample Lets start fromthe sample project and then create the ports and adapters
- 18. 05 Core Use Caseas service
- 19. Implementing the UseCase as Service05 • Domain model • Entities • Repositories • Well defined interface • Input/Output Events • Event Handlers & Translators • Service composition • Unit Testing
- 20.
- 21.
- 22. Implementing passive controllers •Dummy service invokers • Do not perform multiple service calls • It does not make any workflow decision • REST Domain translator 0305 • UC • Service • Services • Domain • Controller REST Domain 06
- 23.
- 24.
- 25. Externalized configuration • Externalfiles • Environment variables • Configuration profiles • Services 030507
- 26.
- 27. Comments • How manyports? • The hexagon is a metaphor • Abstractions • Use Case as port • Module as port: Notification, Administration, Public API, Database 0303 • Services
- 28. See more… • RESTfulAPI with Spring Boot • Securing REST APIs • References: [1] alistair.cockburn.us/Hexagonal+architecture [2] www.infoq.com/news/2013/08/hexagonal-lifepreserver-spring [3] github.com/russmiles/life-preserver-introductory-article-developer-magazine/ blob/master/README.md [4] github.com/spring-guides/deprecate-tut-rest [5] blog.ploeh.dk/2013/12/03/layers-onions-ports-adapters-its-all-the-same / fabricioepa.wordpress.com
- 29. Contact FABRICIO EPAMINONDAS 0 linkedin.com/in/fabricioepa /fabricioepa.wordpress.com 1 @fabricioepa