Architecture at scale - The Essentials (Tech.Rocks Meetup)

An overview of what you should keep in mind on software architecture at scale, especially if you are a CTO in a growing company.

#coordination #autonomy #decentralization #domain-driven #boundedcontexts #microservices #monolith

Transcript

1. @CYRIUX ARCHITECTURE À L’ÉCHELLE, L’ESSENTIEL MEETUP TECH.ROCKS 11 JUIN 2020 @CYRIUX @AROLLA @LESINGECUIVRE Cyrille Martraire
2. SINCE 1999 CYRILLE MARTRAIRE @CYRIUX @AROLLA @LESINGECUIVRE
3. @CYRIUX OUR COMING EVENTS… https://www.lesingecuivre.com/des-conferences-et-ateliers-inspirants/
4. @CYRIUX 3 POINTS ON ARCHITECTURE IN GENERAL
5. @CYRIUX Frugal Solutions Explicit Goals Reversible Decisions @CYRIUX
6. @CYRIUX Explicit Goals @CYRIUX DON’T TALK SOLUTION WITHOUT A CLEARLY STATED PROBLEM (REAL PROBLEM)
7. @CYRIUX Frugal Solutions ANY SOLUTION BRINGS NEW PROBLEMS (CACHE…)
8. @CYRIUX Reversible Decisions MINIMISE IRREVERSIBLE DECISIONS (KEEP OPTIONS OPEN)
9. @CYRIUX WHAT ABOUT ARCHITECTURE AT SCALE?
10. A LITTLE STORY
11. @CYRIUX ONCE UPON A TIME…
12. @CYRIUX ONE BIG BALL OF EVERYTHING
13. @CYRIUX 1 TEAM
14. @CYRIUX 1 COMPONENT {;}
15. @CYRIUX ANYBODY CAN DO ANYTHING #NoLimit
16. @CYRIUX ANYBODY CAN DO ANYTHING #NoLimit #Versatile
17. @CYRIUX CHEAP. just add code
18. @CYRIUX DEPLOY AT ONCE #GoLive
19. @CYRIUX HOLISTIC GROWTH & EVOLUTION! #better
20. @CYRIUX HOLISTIC GROWTH & EVOLUTION! #better innovate. pivot. big shift.
21. @CYRIUX LIFE’S GOOD!
22. @CYRIUX TIME PASSED…
23. @CYRIUX AND ONE DAY…
24. @CYRIUX TOO MANY PEOPLE
25. @CYRIUX INTERFERING ON EACH OTHER’S WORK
26. @CYRIUX OR TOO MUCH COORDINATION #TooManyMeetings
27. @CYRIUX DELIVERY SLOWING DOWN #Slow
28. @CYRIUX FRUSTRATION #sad
29. @CYRIUX THEY KNEW THE SOLUTION…
30. @CYRIUX SPLIT! @CYRIUX
31. @CYRIUX SPLIT! @CYRIUX
32. @CYRIUX SPLIT! @CYRIUX
33. @CYRIUX 1. @CYRIUX
34. @CYRIUX MANY. @CYRIUX
35. @CYRIUX 1 COMPONENT {;} @CYRIUX
36. @CYRIUX MANY COMPONENTS {;} {;} {;} {;} @CYRIUX
37. @CYRIUX 1 TEAM @CYRIUX
38. @CYRIUX MANY TEAMS @CYRIUX
39. @CYRIUX LARGE @CYRIUX
40. @CYRIUX small small small small @CYRIUX
41. @CYRIUX FRUSTRATION @CYRIUX
42. @CYRIUX LIFE’S GOOD AGAIN @CYRIUX
43. @CYRIUX THEY KNEW THE TECHNOLOGIES…
44. @CYRIUX PaaS Serverless Containers CI/CD pipelines Orchestrators @CYRIUX
45. @CYRIUX THEY KNEW THE PRACTICES…
46. @CYRIUX microservices Event-Driven Architecture API’s BFF Gateways @CYRIUX
47. @CYRIUX BUT STILL, HOW TO DECIDE THE BOUNDARIES?
48. @CYRIUX @CYRIUX ?
49. @cyriux @CYRIUX
50. BOUNDED CONTEXTS @CYRIUX
51. BOUNDED CONTEXTS @CYRIUX since 2003
52. BOUNDED CONTEXTS @CYRIUX before it was cool
54. in autonomy
55. @cyriux @cyriux
56. @cyriux @cyriux
57. @cyriux @cyriux
58. @CYRIUX @CYRIUX
59. @CYRIUX @CYRIUX
60. @CYRIUX @CYRIUX
61. @CYRIUX @CYRIUX
62. @CYRIUX HOW NOT TO HOW TO @CYRIUX
63. @cyriux
64. @cyriux
65. @CYRIUX HOW NOT TO @CYRIUX
66. Split by layer W eb Logic Dao DB @cyriux
67. Split by layer W eb Logic Dao DB EASY
68. @cyriux
69. Split by technology EJB ongoDB ode.js
70. Split by technology EJB ongoDB ode.js EASY
71. @cyriux random results
72. Split by Entity User roduct urchase
73. Split by Entity User roduct urchase EASY
74. @cyriux worst results
75. @CYRIUX HOW TO @CYRIUX
76. Split by Functional Area aym ent atalogue hipping Billing
77. DESIGN DECISION Functional areas
78. e-commerce Bounded Contexts • SEO, Traffic Acquisition • Marketing & Targeting • PIM (Product Identification Management) • Catalogue • Categorization • Search • Recommendation • Pricing, Promotions • Basket • Discount, Loyalties • Shipping Cost Estimation • Payment • (Fraud Detection) • Order Management • Billing • Stock / Overbooking • Shipping • Return • CRM
79. How do we identify Bounded Contexts? 79
80. 80 How do we identify Sub Domains?
81. @CYRIUX Focus on the language @CYRIUX
82. Payment Event Anomaly Agent Transaction Transaction Status Account Basket Items Recent Baskets
83. Payment Event Anomaly Agent Transaction Transaction Status Account Basket Items Recent Baskets
84. Payment Event Anomaly Agent Transaction Transaction Status Account Basket Items Recent Baskets Shopping Cart Payment Payment Fraud Detection
85. Sub-Domains Names • Often end in ”-ing” or ”-tion” • Because purpose verbs made into nouns HEURISTICS
86. @CYRIUX Focus on the purpose @CYRIUX
87. THE SAME THING IN THE REAL WORLD (EG A CUSTOMER) FOR DIFFERENT PURPOSES BECOMES DIFFERENT THINGS
88. Different perspectives MY catalogue/book is not YOUR shipping/book
89. “At Amazon, what a book is for you?” •Catalog: Picture, title, authors, rating, format (ebook or paper), category •Recommandation: List of books often bought together with it •Shipping: Dimensions, weight, international restrictions due to content •Shopping cart: Price, discount eligible •Customer review: List of (rating, review, review rating) •Book Search: title, isbn, authors •Search Inside!: full-text content, copyright- dealing policy thx @gweinbach
90. @CYRIUX Focus on the Kind of Complexity @CYRIUX
91. SECRET SAUCE? OR NECESSARY BURDEN? (don’t mix them)
92. @CYRIUX Mixing All Your Mental Models @CYRIUX
93. • Directors by departments (Marketing, Sales, Operations, Customer Support…) • Interviews people and listen to their purpose & language
94. Pre-Negotiation Listing) B2BOrdering Fraud Détection Payment Sourcing Distribution Rates Grid RealTime Prices Gift Cards Content & Comparators Sales Promotion Acquisition TV Campaigns Online Ads Company Rating Product Reviews Shopping Cart Catalogue Search Categories Tags Partnerships Secondary Listing Internal Purchasing Rates CrossSales Navigation SEO Marketing
95. Event Storming PRACTICE
96. Sub-Domain A sub-sub domain A1 sub-sub domain B1 sub-sub domain C1 Domain Sub-Domain B Sub-Domain C sub-sub domain A2 sub-sub domain C2 Customers Experience X1 Customers Experience X2 Customers Experience X3 Generic enabler Audience Experiences Business (Sub)- Domains Domain- agnostic Enablers Collaborators Experience X4 Very specific Generic Specific audience Domain- Specific Domain- Agnostic Volatile Stable MAPPING THE POTENTIAL BOUNDED CONTEXTS
97. @CYRIUX GUIDING DELIVERY PROJECTS @CYRIUX Don’t split for the sake of it. Split Opportunistically when needed. Never fully done.
98. Mapping the Potential Bounded Contexts Sub-Domain A sub-sub domain A1 sub-sub domain B1 sub-sub domain C1 Domain Sub-Domain B Sub-Domain C sub-sub domain A2 sub-sub domain C2 Customers Experience X1 Customers Experience X2 Customers Experience X3 Generic enabler Audience Experiences Business (Sub)- Domains Domain- agnostic Enablers Collaborators Experience X4 Very specific Generic Specific audience Domain- Specific Domain- Agnostic Volatile Stable legacy components not aligned (at all)
99. @CYRIUX (Like Cellular Division)
100. @CYRIUX (Like Cellular Division)
101. @CYRIUX Escape the Tyranny of ONE @CYRIUX
102. @cyriux Fraud Détection Payment Gift Cards n mpany ting Review Shopping Cart EVENT-SOURCED HEXAGONAL ARCHITECTURE CRUD SaaS
103. @cyriux Fraud Détection Payment Gift Cards n mpany ting Review Shopping Cart CASSANDRA POSTGRES ORACLE MongoDB
104. @cyriux Fraud Détection Payment Gift Cards n mpany ting Review Shopping Cart Azure API APP on-premise Azure/WEbapp SaaS Azure FUNCTIONS Azure ML
105. @cyriux Fraud Détection Payment Gift Cards n mpany ting Review Shopping Cart PERF TEST HERE!
106. @cyriux Fraud Détection Payment Gift Cards n mpany ting Review Shopping Cart REWRITE EXTERNALIZE KEEP AS-IS KEEP EXTRACT EXTRACT AS LIB
107. @cyriux Fraud Détection Payment Gift Cards n mpany ting Review Shopping Cart NOW WHEN NECESSARY NEXT YEAR LATER Q3 Q4
108. @cyriux Fraud Détection Payment Gift Cards n mpany ting Review Shopping Cart API API API API API API
109. @cyriux
110. @CYRIUX BUT AFTER THE FIRST VICTORY…
111. @CYRIUX CAME NEW CHALLENGES…
112. @CYRIUX Data Sharing Contracts Deployment Units @CYRIUX
113. @CYRIUX Contracts EXPLICIT COORDINATION TO DEFINE STABLE CONTRACTS → ENABLE BOTH SIDES TO CHANGE FREELY
114. @CYRIUX Contracts ACKNOWLEDGE ALL CONTRACTS! DON’T F**ING BREAK THEM!
115. @CYRIUX Data Sharing @CYRIUX DATA SHARING - SYNC QUERY OR - DB VIEWS OR - IMMUTABLE - VERSIONED - EVENT-DRIVEN MESSAGING ONLY ONE AUTHORITY FOR EACH DATA (data licence?)
116. @CYRIUX Deployment Units @CYRIUX
117. MAPPING THE POTENTIAL BOUNDED CONTEXTS Sub-Domain A sub-sub domain A1 sub-sub domain B1 sub-sub domain C1 Domain Sub-Domain B Sub-Domain C sub-sub domain A2 sub-sub domain C2 Customers Experience X1 Customers Experience X2 Customers Experience X3 Generic enabler Audience Experiences Business (Sub)- Domains Domain- agnostic Enablers Collaborators Experience X4 Very specific Generic Specific audience Domain- Specific Domain- Agnostic Volatile Stable
118. Sub-Domain A sub-sub domain A1 sub-sub domain B1 sub-sub domain C1 Domain Sub-Domain B Sub-Domain C sub-sub domain A2 sub-sub domain C2 Customers Experience X1 Customers Experience X2 Customers Experience X3 Generic enabler Audience Experiences Business (Sub)- Domains Domain- agnostic Enablers Collaborators Experience X4 Very specific Generic Specific audience Domain- Specific Domain- Agnostic Volatile Stable SpringBoot Postgres / Elastic Search RabbitMQ Microservice MAPPING THE POTENTIAL BOUNDED CONTEXTS
119. MAPPING THE TARGET ARCHITECTURE Sub-Domain A sub-sub domain A1 sub-sub domain B1 sub-sub domain C1 Domain Sub-Domain B Sub-Domain C sub-sub domain A2 sub-sub domain C2 Customers Experience X1 Customers Experience X2 Customers Experience X3 Generic enabler Audience Experiences Business (Sub)- Domains Domain- agnostic Enablers Collaborators Experience X4 Very specific Generic Specific audience Domain- Specific Domain- Agnostic Volatile Stable Modular Monolith
120. @CYRIUX CALL TO ACTION from where you are, CONSIDER: WHERE TO SPLIT NEXT? ON WHAT BOUNDARIES? ACKNOWLEDGE: WHAT CONTRACTS ARE ALREADY THERE, EVEN IMPLICITLY? START QUESTIONING: WHO REALLY OWNS EACH PIECE OF DATA?
121. @CYRIUX OUR COMING EVENTS… https://www.lesingecuivre.com/des-conferences-et-ateliers-inspirants/
122. @cyriux BUY MY BOOK!
123. @CYRIUX THE END THANK YOU @AROLLA @LESINGECUIVRE