Ddd(meetup 2) ddd with clean architecture
3 likes611 views
The document discusses the concepts of clean architecture and domain-driven design (DDD). It explains that clean architecture aims to minimize human resources required to build and maintain systems by separating components by scope and lifetime, with inner layers protected from outer ones. DDD models a system based on its domain and business rules, dividing it into bounded contexts and aggregates. The document argues that combining clean architecture and DDD can produce systems that are flexible, independent and organized around domain concepts.
Ddd(meetup 2) ddd with clean architecture
- 1. QRCode 1
- 2. DDD with Clean Architecture 0 1 2
- 3. ? 3
- 4. , 4
- 5. ? 5
- 6. 6
- 7. 7
- 8. … PM ? 8
- 9. , , , || 9
- 10. “The goal of software architecture is to minimize the human resources required to build and maintain the required system.” Robert C. Martin – Clean Architecture minimize 10
- 11. 11
- 12. 12
- 13. ? , ? ! 13
- 14. 14
- 15. - 15
- 16. +: -: 16
- 18. - 18
- 20. 20
- 21. … 21
- 22. … 22
- 23. ? 23
- 24. 24
- 25. ? ! ! DDD ! 25
- 26. • • • 26
- 27. ? 27
- 28. 28
- 29. , 29
- 30. ? 30
- 31. …. 31
- 33. 33
- 34. 34
- 35. 35
- 36. Vision Planning Strategy Doing Teamwork Consistency Success / 36
- 37. - 37
- 38. ? 38
- 39. - 39
- 40. ? 40
- 41. - 41
- 42. ? 42
- 43. - 43
- 44. ? 44
- 45. 45
- 46. ? 46
- 47. 47
- 48. Component + Layer + • : Component • : Layer 48
- 49. - 49
- 50. 50
- 51. - 51
- 52. , 52
- 53. Coding , ! 53
- 54. 54
- 55. - 55
- 56. - : 56
- 57. - & 57
- 58. 58
- 59. 59
- 60. SOLID DRY 60
- 61. SOLID 61
- 62. DRY ? 62
- 63. DRY “Every piece of knowledge must have a single, unambiguous, authoritative representation within a system” Andy Hunt – The Pragmatic Programmer 63
- 64. DRY Code … 64
- 65. DRY - & , 65
- 66. 66
- 67. I/O, , 67
- 69. - 69
- 70. , =0 70
- 73. (Capture)- (1) • (Aircraft) (Departure), (Destination) • , 73
- 74. (Capture)- (2) • (Route) • (Departure) 74
- 75. (Capture)- (3) • , (Fix) • 3 (3DPoint) 75
- 76. (Capture)- (4) • , 2D (2DPoint) 76
- 77. DDD Aggregate 77
- 78. , , - , ! ? 78
- 79. 79
- 81. 81
- 83. ? 83
- 84. - Port and Adapter 84
- 85. DDD 85
- 86. 86
- 87. -Use Case 87
- 88. Clean Architecture 88 (Core Subdomain) (Supporting Subdomain) (Supporting Subdomain) (General Subdomain) (Problem Domain)
- 90. 90
- 91. 91
- 92. (Pattern) An architectural pattern is a general, reusable solution to a commonly occurring problem in software architecture within a given context. Architectural patterns are often documented as software design patterns. Following traditional building architecture, a ‘software architectural style’ is a specific method of construction, characterized by the features that make it notable -- by Wiki 92
- 93. (Style) An architectural style defines: a family of systems in terms of a pattern of structural organization; a vocabulary of components and connectors, with constraints on how they can be combined. Architectural styles are reusable ‘packages’ of design decisions and constraints that are applied to an architecture to induce chosen desirable qualities. -- by Wiki 93
- 94. 94
- 96. Recap • • • • , • : (CEP) Capture + Embedded + Protect • • / 96
- 97. , 97