Architecting For Scale

@duffleit The Art of Architecting for Scale @duﬄeit

@duffleit DAVID LEITNER Principal Engineer 👋 [email protected] 🌎 @duffleit

@duffleit 📦 👧 🧑 👧 🧑 👧 🔥 Safely and
sustainably reduce lead time to thank you. Daniel Terhorst-North Complex System

@duffleit 🔥 🔴 Simple System

@duffleit 🥳 🟢 Simple System

@duffleit Simple System

@duffleit Complicated System 🔥 🔴

@duffleit Complicated System

@duffleit Complicated System Module A Module B Module C

@duffleit Complicated System Distributed Systems Service A Service B Service
C

@duffleit Deployment Units Monolithical Distributed Modularisa3on Bad Well Big Ball
Of Mud

@duffleit “Sadly, architecture has been undervalued for so long that
many engineers regard life with a BIG BALL OF MUD as normal.“ Foote & Yoder

@duffleit Deployment Units Monolithical Distributed Modularisation Bad Well Big Ball
Of Mud Distributed MOnolith WelL-Structured MOdulith

@duffleit There is a multitude of reasons to go for
Distributed Systems. Modularisation is none of them.

@duffleit Module A Module B Module C Single Deployment Unit

@duffleit Service A Service B Serivice C

@duffleit Service A Service B Serivice C Individual Scaling Demand
10x Users Usual Traﬃc

@duffleit Service A Service B Serivice C Individual Scaling Demand
Technology Segmentation

@duffleit Service A Service B Serivice C

@duffleit Service A Service B Serivice C 👧 🧑 🧑
👧 🧑 🧑 👧 🧑 🧑 Ownership You build it, You Own it You build it, You Run it

@duffleit Single Deployment Unit MOdule A MOdule B MOdule C
👧 🧑 🧑 👧 🧑 🧑 👧 🧑 🧑 Ownership You build it, You Own it You build it, You Run it 🔥

@duffleit Single Deployment Unit MOdule A MOdule B MOdule C
👧 🧑 🧑 👧 🧑 🧑 👧 🧑 🧑 Ownership You build it, You Own it You build it, You Run it 🔥 🔥

@duffleit Service A Service B Serivice C 👧 🧑 🧑
👧 🧑 🧑 👧 🧑 🧑 Take Ownership and Responsibility

@duﬄeit 👧 🧑 🧑👧 🧑 🧑 👧 🧑 🧑 📦

@duﬄeit 📦 📦 👧 🧑 🧑 📦 👧 🧑 🧑
👧 🧑 🧑

@duffleit Deployment Units Monolithical Distributed Modularisation Bad Well Big Ball
Of Mud WelL-Structured Modulith Distributed Monolith Autonomous Service-Based Architecture

@duffleit Deployment Units Monolithical Distributed Modularisation Bad Well Complex Distributed
System Complicated Monolithical System

@duffleit 👧 🧑 🧑👧 🧑 🧑 👧 🧑 🧑 🔴
🔥 🟢 Complicated Monolithical System Lending System Age Calculation

@duﬄeit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑
🧑 🔴 🔴 Complex Distributed System Lending System Loan Team

@duﬄeit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑
🧑 🔴 🔴 🔴 Complex Distributed System Lending System Loan Team

@duffleit Rela%on Between Root Cause and Eﬀect Complex Distributed System
Complicated Monolithical System is usually given is usually not given

@duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑
🧑 🔴 🔴 🔴 Complex Distributed System

@duﬄeit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑
🧑 🔴 Complex Distributed System

@duffleit What’s the diﬀerence between a method call within a
single deployment unit

@duffleit What’s the difference between a method call within a
single deployment unit Deployment Unit Module A Module B moduleB.createUser() fun createUser() { /*...*/ }

single deployment unit, and a method call across the network. Deployment Unit Deployment Unit Service A Service B restClient.user() fun createUser() { /*...*/ }

single deployment unit, and a method call across the network. Everything.

@duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑
🧑 🔴 Complex Distributed System https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing

@duﬄeit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑
🧑 🔴 Complex Distributed System

@duffleit Rela%on Between Root Cause and Eﬀect Complex Distributed System
Complicated Monolithical System is usually given is usually not given Cause of Failures reliability availability

@duﬄeit 📦 📦 👧 🧑 🧑 📦 👧 🧑 🧑
👧 🧑 🧑

@duffleit 📦 📦 👧 🧑 🧑 📦 👧 🧑 🧑
👧 🧑 🧑 🔥

@duﬄeit 📦 📦 👧 🧑 🧑 📦 👧 🧑 🧑
👧 🧑 🧑 🤯

@duﬄeit Relation Between Root Cause and Effect Complex Distributed System

@duffleit Relation Between Root Cause and Effect Complex Distributed System

@duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 🔴 Complex
Distributed System 👧 🧑 🧑 Online Shopping System Store Team Warehouse Team

@duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 🔴 🔴
Complex Distributed System 👧 🧑 🧑 🟢 Store Team Warehouse Team

@duﬄeit 👧 🧑 🧑 🔥 👧 🧑 🧑 Complex Distributed
System 👧 🧑 🧑 🔴 Store Team Warehouse Team

@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.

@duffleit We need to architect with Failure in Mind.

@duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 Payment
Service 🧑 Accout Service Online Shopping System

@duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴
Payment Service 🧑 Accout Service 🔥 Users[] 🔥

@duﬄeit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴
Payment Service 🧑 Accout Service Users[] 🔥

@duﬄeit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴
Payment Service 🧑 Accout Service Users[] cache

@duﬄeit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴
Payment Service 🧑 Accout Service Users[] stream UserChanged

@duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴
Payment Service 🧑 Accout Service projection stream Users[] UserChanged

Service 🧑 Accout Service projection stream 🔥🔥 🔥 🔥 Users[]

Service 🧑 Accout Service 🔥 🚀 LBs CBs Caching

@duffleit We need to architect with Failure, and for Scale,
in Mind.

@duffleit Services that can run in a chaotic environment can
run everywhere. Services that can only run in stable environment can only run there.

@duffleit 👧 🧑 🧑 🔥 👧 🧑 👧 🧑 🧑
🔴 Payment Team 🧑 Accout Team Execute Payment Payment Gateway Team

@duﬄeit 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 Payment
Team 🧑 Accout Team 🤯

@duffleit < 👧 🧑 🧑 🔥 SEPA Payment Team Accout
Team Execute Payment CREDITCARD Payment Team < 👧 🧑 🧑 🧑 👧 🧑

@duﬄeit < 👧 🧑 🧑 🔥 SEPA Payment Team Accout
Team Execute Payment CREDITCARD Payment Team < COMPLICATED process 👧 🧑 🧑 COMPLICATED process 🧑 👧 🧑 😌

@duﬄeit 👧 🧑 🧑 🔥 🔴 Payment Team Accout Team
Execute Payment Payment Gateway Team COMPLEX process 👧 🧑 🧑 👧 🧑 🧑

@duffleit We need to architect for End-2-End Customer Journeys.

@duffleit < SEPA Payment Team Accout Team FRAUD CHECK <
🧑 👧 🧑 👧 🧑 🧑 Core Team 👧 🧑 🧑

@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

@duffleit Can our service have 99,99% availability if our dependencies
has a 99,9% availability?

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?

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?

CHECK < 🧑 👧 🧑 👧 🧑 🧑 Core Team 👧 🧑 🧑 MTTF? Platform teams SLAs

@duffleit We need to architect based on Availability.

👧 🧑 🧑 Legacy System 👧 🧑 🧑 👧 🧑 🧑

👧 🧑 🧑 Legacy System 👧 🧑 🧑

@duffleit Readers Writers Writers Readers API User Fraud Data User
Fraud Data ⏳ Downtime Given

@duffleit Readers Writers Writers Readers API User Fraud Data User
Fraud Data 🔥

@duﬄeit Readers Writers Writers Readers API User Fraud Data User
Fraud Data 🔥

@duffleit CDC Readers Writers Writers Readers API User Fraud Data
User Fraud Data

Events User Fraud Data

Events User Fraud Data 🔥

Events User Fraud Data 👷

Events User Fraud Data Zero-Downtime Migration

@duﬄeit We need to architect with a non-negotiable Zero-Downtime Mindset.

@duﬄeit We need to Start Dacining with the Beast

@duﬄeit 👧 🧑 🧑 👧 🧑 🧑 Complex Distributed System
👧 🧑 🧑 Gamedays 🤡 🤡 🤡 Payment Team

@duffleit We embrace Chaos in our architecture.

@duffleit So many thing to consider, Let’s sum up.

@duffleit Complex Distributed System Deployment Units Monolithical Distributed Complicated Monolithical
System Modularisation is no reason to go for Distributed Systems.

@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 💣

@duffleit 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 🧑
🔥

@duffleit 📦 👧 🧑 🧑 📦 📦 Keep the Flow
of Value high & the Amount of Outages low. 👧 🧑 🧑 👧 🧑 🧑

@duﬄeit Keep the lead time to Thank You low, even
at scale.

@duﬄeit DAVID LEITNER Principal Engineer 👋 [email protected] 🌎 @duffleit

@duﬄeit squer.link/arch-scale WORKSHOP Architecting for Scale Free Friends & Family
DryRun

Architecting For Scale

Architecting For Scale

More Decks by SQUER Solutions

Other Decks in Programming

Featured

Transcript