Construcción de web-apps: Un enfoque hexagonal

Transcript

1. gustav.onecore.cl
2. Arquitectura “Si en una sala llena de diseñadores de software dos de ellos están de acuerdo, eso es una mayoría” Bill Curtis
3. Simple application Create Projects :) ...yeah right
4. Simple application Create Projects :) ...yeah right
5. Simple application
6. Simple application :(
7. MVC comes to rescue you … I think
8. MVC comes to rescue you Create Project POST /v1/customer/1/project … I think Web endpoint
9. MVC comes to rescue you Create Project POST /v1/customer/1/project … I think Web endpoint Controller/ProjectController
10. MVC comes to rescue you Create Project POST /v1/customer/1/project … I think Web endpoint Controller/ProjectController Concrete Concrete Concrete Concrete Concrete
11. MVC comes to rescue you Create Project POST /v1/customer/1/project … I think Web endpoint Controller/ProjectController Database context Web context Filesystem context
12. Domain logic wired to different contexts Web, HTTP Database, ER manager Controller, Request Create Project
13. Reuse domain logic in other contexts editRepository() Create project
14. Reuse domain logic in other contexts editRepository() Create project How?
15. Can I reuse that code?
16. Summary of pros/cons Pros - Rapid application development (R.A.D) - Low learning curve - Lots of frameworks in any flavour - Good documentation Cons - Rapid application development (R.A.D) → becomes B.A.D (Bad application development) - Too much coupling between layers - Not good abstraction - Technical debt - Domain logic wired to the framework
17. Arquitectura Hexagonal “Hexagonal Architecture is an architecture defined by establishing a perimeter around the domain of your application and establishing adapters for input/output interactions. By establishing this isolation layer, the application becomes unaware of the nature of the things it's interacting with.” Alistair Cockburn
18. Heart of hexagonal architecture Inner things Outside things
19. Heart of hexagonal architecture Inner things Outside things
20. • Decoupled application from dependencies • Ports (have a language) • Adapters (mutate message from port to application). All right, a better explanation Application Port Port Port Port
21. Adapters and Ports HTTP Request Controller Request Form Web Port Mutate Entity Repository
22. Create Project - POST /customer/1/project Create project, a better approach Web endpoint
23. Create Project - POST /customer/1/project Create project, a better approach Web endpoint Web endpoint CreateProject CreateProjectFolder CreateProjectEntity
24. Alright, show me the code... Adapter mutate message from the web port ProjectController
25. Alright, show me the code... Adapter mutate message from the web port ProjectController Good abstraction Context: Create a project
26. Alright, show me the code... Adapter mutate message from the web port CreateProjectCommand ProjectController CreateProjectCommand
27. Hey, but I want to create a command line script too
28. Be solid, ensure the single responsibility principle of your features. Reuse your commands
29. Summary of pros/cons Pros - Low technical debt === good architecture - Decoupled layers - A good approach for complex applications with several developers - Good abstraction for the domain logic - Reuse your beautiful code Cons - It’ not too easy to implement as MVC - In some cases the Hexagonal documentation is too abstract
30. Preguntas?
31. Anexos
32. CommandBus, handler
33. Command
34. Dependency Injection