The Art of Architecting for Scale

Microservice Meetup Munich

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 Monolithic Distributed Modularisation 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 Monolithic 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 If you can’t build a well-structured monolith, what makes you think microservices are the answer? Simon Brown
16. @duffleit Module A Module B Module C Single Deployment Unit
17. @duffleit Service A Service B Serivice C
18. @duffleit Service A Service B Serivice C Individual Scaling Demand 10x Users Usual Traffic
19. @duffleit Service A Service B Serivice C Individual Scaling Demand Technology Segmentation
20. @duffleit Service A Service B Serivice C Individual Scaling Demand Technology Segmentation 🇩🇪 🇩🇪 🇺🇸 CO-Locating
21. @duffleit Service A Service B Serivice C
22. @duffleit Service A Service B Serivice C 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 🧑 Ownership You build it, You Own it You build it, You Run it
23. @duffleit Single Deployment Unit MOdule A MOdule B MOdule C 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 🧑 Ownership You build it, You Own it You build it, You Run it 🔥
24. @duffleit Single Deployment Unit MOdule A MOdule B MOdule C 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 🧑 Ownership You build it, You Own it You build it, You Run it 🔥 🔥
25. @duffleit Service A Service B Serivice C 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 🧑 Take Ownership and Responsibility
26. @duffleit Technical Benefits Organizational Autonomoy Scale Engineering CO-Locating Technology Segmentation Individual Scaling Demand
27. @duffleit Technical Benefits Organizational Autonomoy Scale Engineering CO-Locating Technology Segmentation Individual Scaling Demand 20% 80%
28. @duffleit 👧 🧑 🧑👧 🧑 🧑 👧 🧑 🧑 📦
29. @duffleit 📦 📦 👧 🧑 🧑 📦 👧 🧑 🧑 👧 🧑 🧑
30. @duffleit Deployment Units Monolithic Distributed Modularisa3on Bad Well Big Ball Of Mud WelL-Structured Modulith Distributed Monolith Autonomous Service-Based Architecture
31. @duffleit Deployment Units Distributed Modularisa3on Bad Well Big Ball Of Mud WelL-Structured Modulith Distributed Monolith Autonomous Service-Based Architecture Monolithic
32. @duffleit Deployment Units Monolithic Distributed Modularisation Bad Well Complex Distributed System Complicated Monolithic System
33. @duffleit 👧 🧑 🧑👧 🧑 🧑 👧 🧑 🧑 🔴 🔥 🟢 Complicated Monolithic System Age Calculation Lending System
34. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑 🧑 🔴 🔴 Complex Distributed System Loan Team Lending System
35. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑 🧑 🔴 🔴 🔴 Complex Distributed System Loan Team Lending System
36. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑 🧑 🔴 Complex Distributed System Loan Team Lending System
37. @duffleit Relation Between Root Cause and Effect Complex Distributed System Complicated Monolithical System is usually given is usually not given
38. @duffleit What’s the difference between a method call within a single deployment unit
39. @duffleit What’s the difference between a method call within a single deployment unit Deployment Unit Module A Module B moduleB.createUser() fun createUser() { /*...*/ }
40. @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() { /*...*/ }
41. @duffleit What’s the difference between a method call within a single deployment unit, and a method call across the network. Everything.
42. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑 🧑 🔴 Complex Distributed System
43. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑 🧑 🔴 Complex Distributed System https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing
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 📦 📦 👧 🧑 🧑 📦 👧 🧑 🧑 👧 🧑 🧑
46. @duffleit 📦 📦 👧 🧑 🧑 📦 👧 🧑 🧑 👧 🧑 🧑 🔥
47. @duffleit 📦 📦 👧 🧑 🧑 📦 👧 🧑 🧑 👧 🧑 🧑 🤯
48. @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
49. @duffleit Relation Between Root Cause and Effect Complex Distributed System Complicated Monolithic System is usually given is usually not given Cause of Failures reliability availability
50. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 🔴 Complex Distributed System 👧 🧑 🧑 Loan Team Lending System
51. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 🔴 🔴 Complex Distributed System 👧 🧑 🧑 🟢 Account Team Loan Team Lending System
52. @duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 Complex Distributed System 👧 🧑 🧑 🔴 Loan Team Lending System Account Team
53. @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.
54. @duffleit Failure in Mind. We need to architect with 🔥
55. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 Payment Service 🧑 Account Service 🛍 Online Shopping System
56. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴 Payment Service 🧑 Account Service 🔥 Users[] 🔥 🛍 Online Shopping System
57. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴 Payment Service 🧑 Account Service Users[] 🔥 🛍 Online Shopping System
58. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴 Payment Service 🧑 Account Service Users[] cache 🛍 Online Shopping System
59. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴 Payment Service 🧑 Account Service Users[] stream UserChanged 🛍 Online Shopping System
60. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴 Payment Service 🧑 Account Service projection stream Users[] UserChanged 🛍 Online Shopping System
61. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴 Payment Service 🧑 Account Service projection stream Users[] UserChanged 🛍 Online Shopping System
62. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 Payment Service 🧑 Account Service projection stream 🔥🔥 🔥 🔥 Users[] 🛍 Online Shopping System
63. @duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 Payment Service 🧑 Account Service 🔥 🚀 LBs CBs Caching
64. @duffleit Failure and Scale in Mind. We need to architect with 🔥
65. @duffleit Services that can run in a chaotic environment can run everywhere. Services that can only run in a stable environment can only run there.
66. @duffleit 👧 🧑 🧑 🔥 👧 🧑 👧 🧑 🧑 🔴 Payment Team 🧑 Account Team Execute Payment Payment Gateway Team
67. @duffleit 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 Payment Team 🧑 Account Team 🤯
68. @duffleit < 👧 🧑 🧑 🔥 SEPA Payment Team Account Team Execute Payment CREDITCARD Payment Team < 👧 🧑 🧑 🧑 👧 🧑
69. @duffleit < 👧 🧑 🧑 🔥 SEPA Payment Team Account Team Execute Payment CREDITCARD Payment Team < COMPLICATED End2End flow 👧 🧑 🧑 COMPLICATED End2End flow 🧑 👧 🧑 😌
70. @duffleit 👧 🧑 🧑 🔥 🔴 Payment Team Account Team Execute Payment Payment Gateway Team COMPLEX End2End flow 👧 🧑 🧑 👧 🧑 🧑
71. @duffleit End-2-End Customer Journeys. We need to architect for 🪢
72. @duffleit < SEPA Payment Team Account Team FRAUD CHECK < 🧑 👧 🧑 👧 🧑 🧑 Core Team 👧 🧑 🧑 💁 Check Payment 👩💻
73. @duffleit < SEPA Payment Team Account 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
74. @duffleit Can our service have 99,99% availability if our dependencies have a 99,9% availability?
75. @duffleit < SEPA Payment Team Account 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?
76. @duffleit < SEPA Payment Team Account 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?
77. @duffleit < SEPA Payment Team Account Team Check Payment FRAUD CHECK < 🧑 👧 🧑 👧 🧑 🧑 Core Team 👧 🧑 🧑 MTTF? Platform teams SLAs
78. @duffleit by Availability. We need to architect driven 9⃣
79. @duffleit < SEPA Payment Team Account Team FRAUD CHECK < 👧 🧑 🧑 Legacy System 👧 🧑 🧑 👧 🧑 🧑
80. @duffleit < SEPA Payment Team Account Team FRAUD CHECK < 👧 🧑 🧑 Legacy System 👧 🧑 🧑
81. @duffleit Readers Writers Writers Readers API User Fraud Data User Fraud Data ⏳ Downtime Given
82. @duffleit Readers Writers Writers Readers API User Fraud Data User Fraud Data 🔥
83. @duffleit Readers Writers Writers Readers API User Fraud Data User Fraud Data 🔥
84. @duffleit CDC Readers Writers Writers Readers API User Fraud Data User Fraud Data
85. @duffleit Readers Writers Writers Readers API User Fraud Data Events User Fraud Data CDC
86. @duffleit Readers Writers Writers Readers API User Fraud Data User Fraud Data 🔥 Events CDC
87. @duffleit Readers Writers Writers Readers API User Fraud Data User Fraud Data 👷 Events CDC
88. @duffleit Readers Writers Writers Readers API User Fraud Data User Fraud Data Zero-Downtime Migration Events CDC
89. @duffleit a Zero-Downtime Mindset. We need to architect driven by 🦜
90. @duffleit We need to Start Dacining with the Beast
91. @duffleit 👧 🧑 🧑 👧 🧑 🧑 Complex Distributed System 👧 🧑 🧑 Gamedays 🤡 🤡 🤡 Payment Team
92. @duffleit Chaos. We need to embrace 💣
93. @duffleit So many thing to consider, Let’s sum up.
94. @duffleit Complex Distributed System Deployment Units Monolithic Distributed Complicated Monolithic System Modularisation is no reason to go for Distributed Systems.
95. @duffleit Failure and Scale in Mind. We need to architect with 🔥 End-2-End Customer Journeys. We need to architect for 🪢 By Availability. We need to architect driven 9⃣ A Zero-Downtime Mindset. We need to architect with 🦜 Chaos. We need to embrace 💣
96. @duffleit 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 🧑 🔥
97. @duffleit 📦 👧 🧑 🧑 📦 📦 Keep the Flow of Value high & the Amount of Outages low. 👧 🧑 🧑 👧 🧑 🧑
98. @duffleit Keep the lead time to Thank You low, even at scale.
99. @duffleit DAVID LEITNER Principal Engineer 👋 david@squer.io 🌎 @duffleit
100. @duffleit squer.link/arch-scale WORKSHOP Architecting for Scale Free Friends & Family DryRun