Architecting Distributed Systems at Scale — From Pain to Pattern

Microservices, Reactive & Distributed Systems Vienna Meetup

Transcript

1. bento.me/david-leitner From Pain to Pattern Architecting Distributed Systems at Scale David Leitner
2. bento.me/david-leitner Chapter 1: Why Words Fail Us Chapter 2: Autonomy as the Driver of Architecture Chapter 3: Economies of Scope Over Scale Chapter 4: Integration Defines Constraints Chapter 5: Time Can’t Be Trusted (Yet) Chapter 6: Resilience Depends on Who You Are Agenda:
3. bento.me/david-leitner we are Doing consulting a bit differently than you might be used to.
4. bento.me/david-leitner Chapter: Why Words Fail Us
5. bento.me/david-leitner Is this a microservice architecture?
6. bento.me/david-leitner And what do these dotted lines actually mean? But this is a microservice architecture, right?
7. bento.me/david-leitner Oh no, this can’t possibly be a microservice architecture now!
8. bento.me/david-leitner Easy now: this is a serverless architecture.
9. bento.me/david-leitner
10. bento.me/david-leitner You've now made it obviously event-driven.
11. bento.me/david-leitner And added a synchronous REST endpoint.
12. bento.me/david-leitner And added a synchronous REST endpoint. 202 ACCEPTED that acts asynchronously.
13. bento.me/david-leitner Different Background, Experience & Context.
14. bento.me/david-leitner Ludwig Wittgenstein Austrian Philosopher “All philosophy is a critique of language.” most traditional philosophical problems are not real problems they're just the result of confused language.
15. bento.me/david-leitner Just as we define a Ubiquitous Language for the Problem Space, we should also build a shared Pattern Language for the Solution Space.
16. bento.me/david-leitner An Architectural Pattern Language This will also accelerate improvements in the quality of your ADRs.
17. bento.me/david-leitner Architecting highly scaled systems isn’t about being the smartest person in the room. It’s about creating a shared understanding of what we are optimizing for. Chapter 1:
18. bento.me/david-leitner Chapter: Autonomy as the Driver of Architecture
19. bento.me/david-leitner economies of scale if you do more of it, it gets faster.
20. bento.me/david-leitner if you do more of it, it slows down & breaks all the time. economies of software engineering
21. bento.me/david-leitner if you do more of it, it slows down & breaks all the time. economies of software engineering
22. bento.me/david-leitner The Exponential Growth of Communication. 2 People 5 People 2 People 18 People
23. bento.me/david-leitner We at conducted a study * * Still not representative due to a sample size that is still too small. … We asked teams what slows them down, decreases their velocity, and negatively impacts their developer experience. The percentages in red show the issues that are located outside of the team. The larger the organization gets, the higher the (unweighted) number of issues that can only be resolved externally. …
24. bento.me/david-leitner
25. bento.me/david-leitner Architecture is a function of its organization: fun(organization) = architecture
26. bento.me/david-leitner fun(UCV) = architecture fun(UCV) = organization Maximize | Org ∩ Architecture | Organizations change. Technologies change. Business values remain surprisingly stable.
27. bento.me/david-leitner Let T = number of teams involved in a change Let S = number of services that must be redeployed Multiplier to define Accidental Complexity of Change = T × S That’s what good architecture should optimize against.
28. bento.me/david-leitner Let’s stop wasting time debating which library is the right one and start aligning architecture with organizational and business goals. Chapter 2:
29. bento.me/david-leitner Chapter: Economies of Scope Over Scale
30. bento.me/david-leitner do not really work for us. Economies of Scale
31. bento.me/david-leitner speed through standardization & reusage. Economies of Scope
32. bento.me/david-leitner Reuse, a desire as old as it is unfulfilled.
33. bento.me/david-leitner Constraining the solution space without narrowing the problem space.
34. bento.me/david-leitner Platform Engineering is a good example of Economies of Scope: squer.io/slides
35. bento.me/david-leitner If your users haven’t built anything that surprises you, then you probably haven’t done a very good job of providing a platform that truly accelerates them. Chapter 3:
36. bento.me/david-leitner Chapter: Integration Define Constraints
37. bento.me/david-leitner Aspects of Integration and How to Decide on Them. 🔥
38. bento.me/david-leitner Patterns of integration have not involved much, as the underlying constraints of the network have mainly remained unchanged. Chapter 4:
39. bento.me/david-leitner Amazon’s Project Kuiper
40. bento.me/david-leitner Chapter: Time Can’t Be Trusted (Yet)
41. bento.me/david-leitner Let’s talk atomic clocks and true time API, and why we need all this.
42. bento.me/david-leitner Either invest a lot of money, and probably still get it wrong or embrace eventual consistency. Chapter 5:
43. bento.me/david-leitner Chapter: Resilience Depends on Who You Are
44. bento.me/david-leitner Resilience is the ability of a system to withstand, recover from, and adapt to failures, disruptions, or unexpected conditions, while maintaining acceptable levels of service and without complete breakdown. Resilience is a dial, not a switch — it's a matter of how much you want to safeguard your system from going down by investing money and effort into it.
45. bento.me/david-leitner Usecase of
46. bento.me/david-leitner Usecase of
47. bento.me/david-leitner You’re not a senior engineer because you’ve implemented lots of happy path. You’re a senior because you’re over-experienced in everything that can go wrong. And will go wrong. Chapter 6:
48. bento.me/david-leitner Chapter 1: Why Words Fail Us Chapter 2: Autonomy as the Driver of Architecture Chapter 3: Economies of Scope Over Scale Chapter 4: Integration Defines Constraints Chapter 5: Time Can’t Be Trusted (Yet) Chapter 6: Resilience Depends on Who You Are Agenda: …to be continued
49. bento.me/david-leitner David Leitner Coding Architect with david@squer.io I’m @duffleit, all accross the www.