Architecting For Scale

CraftConf 2023

Transcript

1. @duffleit The Art of Architecting for Scale @duffleit
2. @duffleit DAVID LEITNER Principal Engineer 👋 david@squer.io 🌎 @duffleit
3. @duffleit 📦 👧 🧑 👧 🧑 👧 🔥 Safely and sustainably reduce lead time to thank you. Daniel Terhorst-North Complex System
4. @duffleit 🔥 🔴 Simple System
5. @duffleit 🥳 🟢 Simple System
6. @duffleit Simple System
7. @duffleit Complicated System 🔥 🔴
8. @duffleit Complicated System
9. @duffleit Complicated System Module A Module B Module C
10. @duffleit Complicated System Distributed Systems Service A Service B Service C
11. @duffleit Deployment Units Monolithical Distributed Modularisa3on Bad Well Big Ball Of Mud
12. @duffleit “Sadly, architecture has been undervalued for so long that many engineers regard life with a BIG BALL OF MUD as normal.“ Foote & Yoder
13. @duffleit Deployment Units Monolithical Distributed Modularisation Bad Well Big Ball Of Mud Distributed MOnolith WelL-Structured MOdulith
14. @duffleit There is a multitude of reasons to go for Distributed Systems. Modularisation is none of them.
15. @duffleit Module A Module B Module C Single Deployment Unit
16. @duffleit Service A Service B Serivice C
17. @duffleit Service A Service B Serivice C Individual Scaling Demand 10x Users Usual Traffic
18. @duffleit Service A Service B Serivice C Individual Scaling Demand Technology Segmentation
19. @duffleit Service A Service B Serivice C
20. @duffleit Service A Service B Serivice C 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 🧑 Ownership You build it, You Own it You build it, You Run it
21. @duffleit Single Deployment Unit MOdule A MOdule B MOdule C 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 🧑 Ownership You build it, You Own it You build it, You Run it 🔥
22. @duffleit Single Deployment Unit MOdule A MOdule B MOdule C 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 🧑 Ownership You build it, You Own it You build it, You Run it 🔥 🔥
23. @duffleit Service A Service B Serivice C 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 🧑 Take Ownership and Responsibility
24. @duffleit 👧 🧑 🧑👧 🧑 🧑 👧 🧑 🧑 📦
25. @duffleit 📦 📦 👧 🧑 🧑 📦 👧 🧑 🧑 👧 🧑 🧑
26. @duffleit Deployment Units Monolithical Distributed Modularisation Bad Well Big Ball Of Mud WelL-Structured Modulith Distributed Monolith Autonomous Service-Based Architecture
27. @duffleit Deployment Units Monolithical Distributed Modularisation Bad Well Complex Distributed System Complicated Monolithical System
28. @duffleit 👧 🧑 🧑👧 🧑 🧑 👧 🧑 🧑 🔴 🔥 🟢 Complicated Monolithical System Lending System Age Calculation
29. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑 🧑 🔴 🔴 Complex Distributed System Lending System Loan Team
30. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑 🧑 🔴 🔴 🔴 Complex Distributed System Lending System Loan Team
31. @duffleit Rela%on Between Root Cause and Effect Complex Distributed System Complicated Monolithical System is usually given is usually not given
32. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑 🧑 🔴 🔴 🔴 Complex Distributed System
33. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑 🧑 🔴 Complex Distributed System
34. @duffleit What’s the difference between a method call within a single deployment unit
35. @duffleit What’s the difference between a method call within a single deployment unit Deployment Unit Module A Module B moduleB.createUser() fun createUser() { /*...*/ }
36. @duffleit What’s the difference between a method call within a single deployment unit, and a method call across the network. Deployment Unit Deployment Unit Service A Service B restClient.user() fun createUser() { /*...*/ }
37. @duffleit What’s the difference between a method call within a single deployment unit, and a method call across the network. Everything.
38. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑 🧑 🔴 Complex Distributed System https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing
39. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑 🧑 🔴 Complex Distributed System
40. @duffleit Rela%on Between Root Cause and Effect Complex Distributed System Complicated Monolithical System is usually given is usually not given Cause of Failures reliability availability
41. @duffleit 📦 📦 👧 🧑 🧑 📦 👧 🧑 🧑 👧 🧑 🧑
42. @duffleit 📦 📦 👧 🧑 🧑 📦 👧 🧑 🧑 👧 🧑 🧑 🔥
43. @duffleit 📦 📦 👧 🧑 🧑 📦 👧 🧑 🧑 👧 🧑 🧑 🤯
44. @duffleit Relation Between Root Cause and Effect Complex Distributed System Complicated Monolithical System is usually given is usually not given Cause of Failures reliability availability
45. @duffleit Relation Between Root Cause and Effect Complex Distributed System Complicated Monolithical System is usually given is usually not given Cause of Failures reliability availability
46. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 🔴 Complex Distributed System 👧 🧑 🧑 Online Shopping System Store Team Warehouse Team
47. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 🔴 🔴 Complex Distributed System 👧 🧑 🧑 🟢 Store Team Warehouse Team
48. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 Complex Distributed System 👧 🧑 🧑 🔴 Store Team Warehouse Team
49. @duffleit We strive for a stable production. But this is totally elusive in a complex environment. and sometimes chaotic The sooner we accept this, the better.
50. @duffleit We need to architect with Failure in Mind.
51. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 Payment Service 🧑 Accout Service Online Shopping System
52. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴 Payment Service 🧑 Accout Service 🔥 Users[] 🔥
53. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴 Payment Service 🧑 Accout Service Users[] 🔥
54. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴 Payment Service 🧑 Accout Service Users[] cache
55. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴 Payment Service 🧑 Accout Service Users[] stream UserChanged
56. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴 Payment Service 🧑 Accout Service projection stream Users[] UserChanged
57. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴 Payment Service 🧑 Accout Service projection stream Users[] UserChanged
58. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 Payment Service 🧑 Accout Service projection stream 🔥🔥 🔥 🔥 Users[]
59. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 Payment Service 🧑 Accout Service 🔥 🚀 LBs CBs Caching
60. @duffleit We need to architect with Failure, and for Scale, in Mind.
61. @duffleit Services that can run in a chaotic environment can run everywhere. Services that can only run in stable environment can only run there.
62. @duffleit 👧 🧑 🧑 🔥 👧 🧑 👧 🧑 🧑 🔴 Payment Team 🧑 Accout Team Execute Payment Payment Gateway Team
63. @duffleit 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 Payment Team 🧑 Accout Team 🤯
64. @duffleit < 👧 🧑 🧑 🔥 SEPA Payment Team Accout Team Execute Payment CREDITCARD Payment Team < 👧 🧑 🧑 🧑 👧 🧑
65. @duffleit < 👧 🧑 🧑 🔥 SEPA Payment Team Accout Team Execute Payment CREDITCARD Payment Team < COMPLICATED process 👧 🧑 🧑 COMPLICATED process 🧑 👧 🧑 😌
66. @duffleit 👧 🧑 🧑 🔥 🔴 Payment Team Accout Team Execute Payment Payment Gateway Team COMPLEX process 👧 🧑 🧑 👧 🧑 🧑
67. @duffleit We need to architect for End-2-End Customer Journeys.
68. @duffleit < SEPA Payment Team Accout Team FRAUD CHECK < 🧑 👧 🧑 👧 🧑 🧑 Core Team 👧 🧑 🧑
69. @duffleit < SEPA Payment Team Accout Team Check Payment FRAUD CHECK < Core Team 🧑 👧 🧑 👧 🧑 🧑 👧 🧑 🧑 How many Nines? Availability? Nines Percentage Yearly Outage 1 Nine 90% 36,5 days 2 Nines 99% 3,65 days 3 Nines 99,9% 8,76 hours 4 Nines 99,99% 52,56 minutes 5 Nines 99,999% 5,26 minutes 6 Nines 99,9999% 31,5 seconds A Planed Outage is an Outage
70. @duffleit Can our service have 99,99% availability if our dependencies has a 99,9% availability?
71. @duffleit < SEPA Payment Team Accout Team Check Payment FRAUD CHECK < 🧑 👧 🧑 👧 🧑 🧑 Core Team 👧 🧑 🧑 How many Nines? Nines Percentage Yearly Outage 1 Nine 90% 36,5 days 2 Nines 99% 3,65 days 3 Nines 99,9% 8,76 hours 4 Nines 99,99% 52,56 minutes 5 Nines 99,999% 5,26 minutes 6 Nines 99,9999% 31,5 seconds A Planed Outage is an Outage rescheduler Availability?
72. @duffleit < SEPA Payment Team Accout Team Check Payment FRAUD CHECK < 🧑 👧 🧑 👧 🧑 🧑 Core Team 👧 🧑 🧑 How many Nines? Nines Percentage Yearly Outage 1 Nine 90% 36,5 days 2 Nines 99% 3,65 days 3 Nines 99,9% 8,76 hours 4 Nines 99,99% 52,56 minutes 5 Nines 99,999% 5,26 minutes 6 Nines 99,9999% 31,5 seconds 🔴 Availability?
73. @duffleit < SEPA Payment Team Accout Team Check Payment FRAUD CHECK < 🧑 👧 🧑 👧 🧑 🧑 Core Team 👧 🧑 🧑 MTTF? Platform teams SLAs
74. @duffleit We need to architect based on Availability.
75. @duffleit < SEPA Payment Team Accout Team FRAUD CHECK < 👧 🧑 🧑 Legacy System 👧 🧑 🧑 👧 🧑 🧑
76. @duffleit < SEPA Payment Team Accout Team FRAUD CHECK < 👧 🧑 🧑 Legacy System 👧 🧑 🧑
77. @duffleit Readers Writers Writers Readers API User Fraud Data User Fraud Data ⏳ Downtime Given
78. @duffleit Readers Writers Writers Readers API User Fraud Data User Fraud Data 🔥
79. @duffleit Readers Writers Writers Readers API User Fraud Data User Fraud Data 🔥
80. @duffleit CDC Readers Writers Writers Readers API User Fraud Data User Fraud Data
81. @duffleit CDC Readers Writers Writers Readers API User Fraud Data Events User Fraud Data
82. @duffleit CDC Readers Writers Writers Readers API User Fraud Data Events User Fraud Data 🔥
83. @duffleit CDC Readers Writers Writers Readers API User Fraud Data Events User Fraud Data 👷
84. @duffleit CDC Readers Writers Writers Readers API User Fraud Data Events User Fraud Data Zero-Downtime Migration
85. @duffleit We need to architect with a non-negotiable Zero-Downtime Mindset.
86. @duffleit We need to Start Dacining with the Beast
87. @duffleit 👧 🧑 🧑 👧 🧑 🧑 Complex Distributed System 👧 🧑 🧑 Gamedays 🤡 🤡 🤡 Payment Team
88. @duffleit We embrace Chaos in our architecture.
89. @duffleit So many thing to consider, Let’s sum up.
90. @duffleit Complex Distributed System Deployment Units Monolithical Distributed Complicated Monolithical System Modularisation is no reason to go for Distributed Systems.
91. @duffleit Failure and Scale in Mind. Architect with 🔥 End-2-End Customer Journeys Architect for 🪢 By the given Availability Architect driven 🟢 A non-negotiable Zero-Downtime Mindset. Architect around 😌 Embracing Chaos Architect by 💣
92. @duffleit 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 🧑 🔥
93. @duffleit 📦 👧 🧑 🧑 📦 📦 Keep the Flow of Value high & the Amount of Outages low. 👧 🧑 🧑 👧 🧑 🧑
94. @duffleit Keep the lead time to Thank You low, even at scale.
95. @duffleit DAVID LEITNER Principal Engineer 👋 david@squer.io 🌎 @duffleit
96. @duffleit squer.link/arch-scale WORKSHOP Architecting for Scale Free Friends & Family DryRun