Introduction to Clean Architecture - CaquiCoders

https://www.youtube.com/watch?v=8arT9bUz6ko&t=3491s

Transcript

1. Introduction to Clean Architecture Ivan Paulovich
 Stockholm
 Software Architecture Meetup
 June 29th, 2020 https://paulovich.net @ivanpaulovich
2. Paulovich.NET @ivanpaulovich
3. What is the Clean Architecture Style? @ivanpaulovich
4. Each of these architectures produce systems that are: • Independent of Frameworks. • Testable. • Independent of UI. • Independent of Database. • Independent of any external agency. https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html “ @ivanpaulovich
5. @ivanpaulovich
6. Clean Architecture Style @ivanpaulovich Clean Architecture Style
7. Clean Architecture Style @ivanpaulovich Clean Architecture Style Hexagonal Architecture Style Clean Architecture Style @ivanpaulovich
8. Clean Architecture Style @ivanpaulovich Clean Architecture Style Hexagonal Architecture Style Ports and Adapters Pattern Dependency Inversion
 Principle Test-Driven Development Clean Architecture Style @ivanpaulovich
9. Clean Architecture Style Hexagonal Architecture Style Ports and Adapters Pattern Dependency Inversion
 Principle Test-Driven Development Clean Architecture Style Object-Oriented Design
 Principles Use Cases as Central Organizing Structure Pluggable User Interface @ivanpaulovich
10. Hexagonal Architecture Style •Ports and Adapters pattern. •The implementation is guided by tests. •It is decoupled from technology details. @ivanpaulovich
11. Business @ivanpaulovich 11 Ports and Adapters Cloud Messaging UI In Memory Persistence Tests In Memory Messaging SQL
12. Business @ivanpaulovich 12 Ports and Adapters Cloud Messaging UI In Memory Persistence Tests In Memory Messaging SQL Ports
13. Ports
14. Business v @ivanpaulovich 14 Ports and Adapters Cloud Messaging UI In Memory Persistence Tests In Memory Messaging SQL Adapters
15. Adapters
16. Application Unit Test Web Database Domain Primary Actors Secondary Actors @ivanpaulovich 16 Infrastructure Ports and Adapters
17. Use Cases • Use Cases show the intent of a system. • Use Cases are delivery independent. • Use Cases are algorithms that interpret the input to generate the output data. • Use Cases diagrams highlight the Primary and secondary actors. 17 @ivanpaulovich
18. Deposit Use Case @ivanpaulovich
19. Deposit Use Case Input and Output Messages @ivanpaulovich
20. Deposit Use Case Request/Response @ivanpaulovich
21. Controller Use Case Core User Interface @ivanpaulovich Request Response Input Output • Abstract • General • Stable • Consistent • Concrete • Specific • Unstable • Inconsistent
22. Object-Oriented Design Principles
23. Entities Entities Clean Architecture Entities Use Cases Controllers Gatew ays Presenters D evices W eb UI DB External Interfaces @ivanpaulovich •Abstractness increases with stability. •Modules depend in the direction of stability. •Classes that change together are packaged together.
24. Entities Use Cases Controllers Presenters Gateways Devices UI DB Web External Interfaces Abstract,
 General,
 Stable,
 Consistent Concrete,
 Specific, 
 Unstable, Inconsistent Level Clean Architecture @ivanpaulovich
25. The Stable Dependencies Principle¹ ¹Clean Architecture, Robert C. Martin, 2017
26. The Stable Dependencies Principle Infrastructure Web Domain Application
27. The Stable Dependencies Principle Infrastructure Web Domain Application Shinning Framework Shinning Library
28. The Stable Dependencies Principle Infrastructure Web Domain Application Shinning Framework Shinning Library
29. The Stable Dependencies Principle Infrastructure Web Domain Application Shinning Framework Shinning Library
30. Walkthrough an Use Case Controller @ivanpaulovich
31. Walkthrough an Use Case Use Case @ivanpaulovich
32. Walkthrough an Use Case Repository @ivanpaulovich
33. Walkthrough an Use Case Use Case @ivanpaulovich
34. Walkthrough an Use Case Domain Service @ivanpaulovich
35. Walkthrough an Use Case Repository @ivanpaulovich
36. Walkthrough an Use Case Use Case @ivanpaulovich
37. Walkthrough an Use Case Unit of Work @ivanpaulovich
38. Walkthrough an Use Case Use Case @ivanpaulovich
39. Walkthrough an Use Case Use Case @ivanpaulovich
40. Walkthrough an Use Case @ivanpaulovich Controller
41. Testing Strategy
42. A Web of Objects @ivanpaulovich
43. Testing ? ? ? Test Expectations @ivanpaulovich
44. The First Test Deposit Use Case Customer Repository Account Repository Test Expectations @ivanpaulovich
45. The Walking Skeleton Deposit Use Case Customer Repository Account Repository Fakes User Interface @ivanpaulovich
46. Deposit Use Case Customer Repository Account Repository Fakes User Interface Integration Tests s Account Repository Test Customer Repository
47. Tests Overview In Process Out of Process Memory Within the application memory Reads I/O. Secondary memory. Speed Fast Slow Setup Effort Easy to design a variety of cases Requires extensive setup Samples Use Cases, Domain Repositories, Services
48. Software Skeleton Gateways Controllers Use Cases Domain Web Service Repositories Database
49. Unit Tests Gateways Controllers Use Cases Domain Repositories Unit Tests Fake Web Service Fake Repository
50. Integration Tests Gateways Controllers Use Cases Domain Web Service Repositories Database Integration Tests
51. Component Tests Gateways Controllers Use Cases Domain Repositories Component Tests Fake Web Service Fake Repository
52. Test Pyramid Unit Tests Component
 Tests Integration
 Tests
53. Wrapping up Clean Architecture • Clean Architecture is about usage and the use cases are the central organizing structure. • Use cases implementation are guided by tests. • The User Interface and Persistence are designed to fulfil the core needs (not the opposite!). • Defer decisions by implementing the simplest component first. 53 @ivanpaulovich
54. References https://cleancoders.com Clean Code: Component Design Clean Code: SOLID Principles Clean Code: Fundamentals https://github.com/ivanpaulovich/clean-architecture-manga Robert C Martin - Clean Architecture and Design @ivanpaulovich
55. Ask me 2 questions! Fork me on GitHub