Download as PDF, PPTX
Uploaded byMatthias Noback
Advanced Application Architecture (workshop slides)
The document discusses application architecture and describes layers, ports and adapters, and different types of testing. It explains that layered architecture helps define dependency rules and placement of components. Layers should only depend on deeper layers according to the dependency inversion principle. Ports define interfaces that external entities interact with, while adapters translate between ports and infrastructure. The document also outlines unit, integration, acceptance, and system tests and how to balance testing at different levels.
More Related Content
Similar to Advanced Application Architecture (workshop slides)
Advanced Application Architecture (workshop slides)
- 1. ADVANCED APPLICATION ARCHITECTURE I - Layers MatthiasNoback @matthiasnoback
- 2. matthiasnoback/layers- ports-and-adapters- workshop Clone from GitHub Followthe instructions in README.md
- 3. ARCHITECTURE Decisions about couplingand cohesion
- 4. COUPLING How are thingslinked to each other?
- 5. COHESION Which things belongtogether?
- 6. COHESION Which things belongtogether? www.youtube.com/watch?v=N_7DPyxzUzc
- 7. LAYERED ARCHITECTURE An answerto both questions
- 8. LAYERS Help you protectwhat's in a deeper layer
- 9. LAYERS Allow you todefine dependency rules
- 10. LAYERS Define the rightplace to put things
- 11.
- 12. LAYERS Horizontal division (asopposed to...)
- 13.
- 14.
- 15. CLEAN ARCHITECTURE Or "union"architecture
- 16. COHESION A basic setof layers domain application infrastructure
- 17. COUPLING The dependency rule Layersshould only depend on deeper layers
- 18. COUPLING Dependency inversion principle Classesshould always depend on things that are more abstract
- 19. COUPLING Dependency inversion principle low-levelconcreteclass specific abstract interface generic high-level
- 20.
- 21.
- 22. COUPLING Is about dependenciesin code Use Dependency Injection
- 23. LAYER CONVENTIONS Domain layer Domainmodel: ➤ Entities ➤ Value objects ➤ Domain services ➤ Factories Business logic Decisions Data State Behavior
- 24. LAYER CONVENTIONS Application layer ➤Find an object ➤ Change something ➤ Notify something ➤ Get some information Use cases Orchestration
- 25. LAYER CONVENTIONS Infrastructure layer Communicationwith: ➤ HTTP client ➤ Database ➤ Filesystem ➤ Email server ➤ Message broker Connecting the application to the world outside
- 26.
- 27.
- 28. MESSAGING ... is thebig idea
- 29. PORTS (COHESION) Web, CLI,test client, messages, database queries Web Database
- 30.
- 31.
- 32. PORTS... AND ADAPTERS (De)serialization,translation, structural validation HTTP SQL
- 33.
- 34. PORT ADAPTERS ...in theInfrastructure layer
- 35. APPLICATION SERVICES ... inthe Application layer
- 36. DOMAIN MODEL in theDomain layer
- 37.
- 38.
- 39. VALIDATION At different levels Structuralvalidation of messages User-friendly input validation Domain invariant protection
- 40.
- 41.
- 42.
- 43. assignment/06.md A hidden dependencyon the persistence mechanism
- 44. ADVANTAGES OF PORTS& ADAPTERS Offers insight into the application Isolates the low-level details Allows for alternative implementations Helps with testing
- 45.
- 46. UNIT TESTS Testing yourunits of code One class at a time No IO No setup required Mocking only dependencies "you own"
- 47. INTEGRATION TESTS Testing youradapters Maybe multiple classes Including IO Some setup required Mocking no dependencies
- 48. ACCEPTANCE TESTS Testing yourapplication services Multiple classes Use cases Infrastructure stand-ins
- 49. SYSTEM TESTS Testing yourapplication end-to-end The real deal
- 50. TESTING PYRAMID Make itwell-balanced Unit tests Integration tests System tests
- 51.
- 52. assignment/08.md A test doublefor the Persistence port
- 53. assignment/09.md An acceptance testfor the application layer
- 54. A WELL-BALANCED TESTSUITE Adapters can be easily replaced Test suite is fast Feedback is quick Small amount of fragile tests Enables continuous delivery