Cultivating Architecture in an Agile World

@duﬄeit Cultivating Architecture In an Agile World David Leitner

@duﬄeit DAVID LEITNER Coding Architect 👋 [email protected] 🌎 @duffleit

@duﬄeit 📦 👧 🧑 👧 🧑 👧 🔥 Safely and
sustainably reduce lead time to thank you. Daniel Terhorst-North “Good Architecture”

@duﬄeit Simple System

@duﬄeit Complicated System

@duﬄeit Complicated System Module A Module B Module C

@duﬄeit Complicated System Distributed Systems Service A Service B Service
C

@duﬄeit Deployment Units Monolithic Distributed Modularisation Bad Well Big Ball
Of Mud

@duﬄeit “Sadly, architecture has been undervalued for so long that
many engineers regard life with a Big Ball of Mud as normal.“ Foote & Yoder

Of Mud Distributed MOnolith WelL-Structured MOdulith

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

@duﬄeit If you can’t build a well-structured monolith, what makes
you think microservices are the answer? Simon Brown

@duﬄeit Module A Module B Module C Single Deployment Unit

@duﬄeit Service A Service B Serivice C

@duﬄeit Service A Service B Serivice C Individual Scaling Demand
10x Users Usual Traffic

Technology Segmentation

Technology Segmentation 🇩🇪 🇩🇪 🇺🇸 CO-Locating

@duffleit Service A Service B Serivice C Individual Scaling Demand
Technology Segmentation CO-Locating Technical Benefits

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

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

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

@duﬄeit Service A Service B Serivice C 👧 🧑 🧑
👧 🧑 🧑 👧 🧑 🧑 Enable Teams to work autonomously

@duffleit Technical Benefits Team Autonomoy Scale Engineering CO-Locating Technology Segmentation
Individual Scaling Demand 80%

@duffleit We architect for autonomy. This is why we tend
do go for Distributed Systems.

@duffleit Non-Functional Requirements Those requirements which make your software non-functional
if you do not consider them.

@duffleit Scalability Availability Consistency Autonomy Your architecture is a tradeoff.
…

@duffleit Business & Domain Organisation Technology

@duffleit a Threefold Architect needs to navigate the intersections of
NFRs between all socio-technical aspects. Business & Domain Organisation Technology

@duffleit Scalability Availability Consistency Autonomy Your architecture is a tradeoff.
…

@duffleit Scalability Availability Consistency Autonomy Your architecture is a tradeoﬀ.
…

@duffleit Responsibility The ops will hate it Zone The Devs
will Quit Zone Autonomy You build it you Own it You build it you run it You build it you care it

@duffleit Team Autonomy Decision Space Responsibility The ops will hate
it Zone The Devs will Quit Zone Autonomy You build it you Own it You build it you run it You build it you care it Governance

@duﬄeit Team Autonomy Decision Space Responsibility The ops will hate
it Zone The Devs will Quit Zone Autonomy You build it you Own it You build it you run it You build it you care it Governance

@duffleit Team Autonomy Decision Space Responsibility The ops will hate
it Zone The Devs will Quit Zone Autonomy You build it you Own it You build it you run it You build it you care it Governance Fitness Functions ADRs & RFCs Tech Radar Figures of Merit

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

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

@duffleit Deployment Units Monolithic Distributed Modularisa6on Bad Well Big Ball
Of Mud WelL-Structured Modulith Distributed Monolith Autonomous Service-Based SYSTEMS

Of Mud WelL-Structured Modulith Distributed Monolith Autonomous Service-Based SYSTEMS Change in Cause of Failure Reliabilty

@duffleit Deployment Units Monolithic Distributed Modularisa6on Bad Well Big Ball
Of Mud WelL-Structured Modulith Distributed Monolith Autonomous Service-Based SYSTEMS Change in Cause of Failure Reliabilty Availability

@duffleit What’s the difference between a method call within a
single deployment unit

@duffleit What’s the diﬀerence 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 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑
🧑 🔴

@duﬄeit 👧 🧑 🧑 🔥 👧 🧑 🧑 👧 🧑
🧑 🔴 https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing

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

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

@duffleit 📦 📦 👧 🧑 🧑 📦 👧 🧑 🧑
👧 🧑 🧑 🤯

@duﬄeit To architect for Autonomy. We need to Optimize for
Availability.

@duﬄeit Deployment Units Monolithic Distributed Modularisa6on Bad Well Big Ball

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

@duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 🔴 🔥
Complex Distributed System 👧 🧑 🧑 🟢 Account Team Loan Team Lending System

@duffleit 👧 🧑 🧑 🔥 👧 🧑 🧑 Complex Distributed
System 👧 🧑 🧑 🔴 Loan Team Lending System Account Team

@duﬄeit We strive for a stable environment.

@duﬄeit There is no stable environment.

@duﬄeit There is no stable environment. * The sooner we
accept this, the better.

@duﬄeit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 Payment
Service 🧑 Account Service

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

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

@duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🔴
Payment Service 🧑 Account Service Users[] cache

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

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

@duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 Payment
Service 🧑 Account Service readmodel stream 🔥🔥 🔥 🔥 Users[]

@duffleit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 Payment
Service 🧑 Account Service 🔥 🚀 Caching LBs CBs

@duﬄeit Chaotic Environments Architect for 🔥

@duﬄeit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 Payment
Service 🧑 Account Service 🔥 🔥 🔥 🔥

@duffleit we need to start dacining with the beast and
embrace Choas.

@duffleit 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 🧑
Gamedays 🤡 🤡 🤡

@duffleit A System that can run in a stable environment
can run only there.

@duffleit A System that can run in a chaotic environment
can run everywhere.

@duffleit Chaotic Environments Architect for 🔥

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

@duffleit 👧 🧑 🧑 👧 🧑 🧑 👧 🧑 Payment
Team 🧑 Account Team 🤯

@duffleit < 👧 🧑 🧑 SEPA Payment Team Account Team
CREDITCARD Payment Team < 👧 🧑 🧑 🧑 👧 🧑

@duﬄeit < 👧 🧑 🧑 End2End Responsibility SEPA Payment Team
Account Team CREDITCARD Payment Team < End2End Responsibility 👧 🧑 🧑 🧑 👧 🧑 😌

@duﬄeit < 👧 🧑 🧑 End2End Responsibility SEPA Payment Team
Account Team CREDITCARD Payment Team < End2End Responsibility 👧 🧑 🧑 🧑 👧 🧑 😌 We need to keep depenedencies in mind Accounts

@duﬄeit Customer Journey and Entity Data Mismatch Problem

@duﬄeit Customer Journey Entities User Accounts Transactions User Onboarding Payment
Execution Fraud Detection

@duffleit < 👧 🧑 🧑 End2End Responsibility Account Team <
End2End Responsibility 👧 🧑 🧑 🧑 👧 🧑 Accounts

@duﬄeit < 👧 🧑 🧑 End2End Responsibility Account Team <
End2End Responsibility 👧 🧑 🧑 🧑 👧 🧑 Accounts cache 🔥

@duﬄeit < 👧 🧑 🧑 End2End Responsibility Account Team <
End2End Responsibility 👧 🧑 🧑 🧑 👧 🧑 Accounts Account Changed readmodel 🔥

@duﬄeit End-2-End Responsibilities. Architect for 🛶

@duﬄeit End-to-End Autonomy ⚖ Dependencies Decrease Cognitive Load

@duﬄeit < SEPA Payment Team Account Team FRAUD CHECK <
👧 🧑 🧑 Check Payment Complicated Subsystem 👧 🧑 🧑 🧑 👧 🧑

@duffleit < SEPA Payment Team Account Team FRAUD CHECK <
👧 🧑 🧑 Check Payment Complicated Subsystem 👧 🧑 🧑 🧑 👧 🧑 💁🙋

👧 🧑 🧑 Check Payment Complicated Subsystem 👧 🧑 🧑 🧑 👧 🧑 Availability 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 MTBF

@duffleit Can our stream aligned team still have a 99,99%
availability if our complex subsystem dependency has a 99,9% availability?

👧 🧑 🧑 Check Payment Complicated Subsystem 👧 🧑 🧑 🧑 👧 🧑 Availability 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 rescheduler

👧 🧑 🧑 Check Payment Complicated Subsystem 👧 🧑 🧑 🧑 👧 🧑 Availability 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 🔄 rescheduler

@duffleit < Account Team FRAUD CHECK < 👧 🧑 🧑
Check Payment Complicated Subsystem 👧 🧑 🧑 Availability 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 🔄 rescheduler Platform Teams Developer Experience SLOs

@duffleit Pain = Strength x Distance x Volatility Vladik Khononov
Dependencies their three main aspects:

@duffleit Pain = Strength x Distance x Volatility Vladik Khononov
Dependencies

@duffleit Dependencies as a Service Architect for 9⃣

👧 🧑 🧑 Legacy System 👧 🧑 🧑 👧 🧑 🧑

👧 🧑 🧑 Legacy System 👧 🧑 🧑

@duffleit User Fraud Data Readers Writers Readers Writers

@duffleit User Fraud Data Readers Writers Readers Writers API

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

@duffleit Readers Writers Readers Writers API User Fraud Data 🔥

@duffleit User Fraud Data Readers Writers API 🔥 Readers Writers

@duffleit User Fraud Data Readers Writers API Readers Writers

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

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

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

@duffleit Event User Fraud Data Readers Readers Writers API User
Fraud Data Event Writers 👷

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

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

@duﬄeit CDC User Fraud Data Readers Writers API User Fraud
Data Event Readers Writers Canary Releases Zero Downtime Migration Dark Launching A/B Testing Scientist Pattern

@duffleit

@duffleit Rollout when no disagreement within 24 hours and within
10 000 000 comparisons.

@duffleit CDC User Fraud Data Readers Writers API User Fraud
Data Event Readers Writers Canary Releases Zero Downtime Migration Dark Launching A/B Testing Scientist Pattern

@duﬄeit Change Anxiety Architect against 🦜

@duﬄeit So many thing to consider, Let’s sum up.

@duﬄeit Business & Domain Organisation Technology Scalability Availability Consistency Autonomy
…

@duﬄeit Architect for Autonomy. We usually need to

@duﬄeit Responsibility The ops will hate it Zone The Devs
will Quit Zone Autonomy You build it you Own it You build it you run it You build it you care it Team Autonomy Decision Space Governance Fitness Functions ADRs & RFCs Tech Radar Figures of Merit Enablement

@duﬄeit Deployment Units Monolithic Distributed Reliabilty Availability

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

@duﬄeit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🧑
Chaotic Environments Architect for 🔥

@duﬄeit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🧑
Chaotic Environments Architect for 🔥 End-2-End Responsibilities Architect for 🛶

@duﬄeit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🧑
Chaotic Environments Architect for 🔥 End-2-End Responsibilities Architect for 🛶 COMPLICATED Subsystem Teams Dependencies as a Service Architect for 9⃣

@duﬄeit 👧 🧑 🧑 👧 🧑 👧 🧑 🧑 🧑
Chaotic Environments Architect for 🔥 End-2-End Responsibilities Architect for 🛶 COMPLICATED Subsystem Teams Change Anxiety Architect against 🦜 Dependencies as a Service Architect for 9⃣

@duffleit Safely and sustainably reduce lead time to thank you.
Daniel Terhorst-North

@duffleit DAVID LEITNER Coding Architect 👋 [email protected] 🌎 @duﬄeit Slides

Cultivating Architecture in an Agile World

Cultivating Architecture in an Agile World

More Decks by SQUER Solutions

Other Decks in Technology

Featured

Transcript