System Design on Easy Mode
Presented at All Things Open 2023 Presented by Loren Sands-Ramshaw - Temporal Title: System Design on Easy Mode Abstract: You know those system design questions you get when interviewing for senior or staff eng roles? I love them. And while I won't solve them all for you, I will teach you an easy way to solve a large class of them. I'll take you through a whirlwind of distributed systems patterns like event-driven architecture, choreography & orchestration, task queues, sagas, circuit breakers, and transactional outboxes, and I'll explain how each is either trivial or unnecessary to implement when we use a new programming primitive called durable execution. We're used to working with volatile execution—the process running our code could die at any time, perhaps due to a crash or pod rotation—and it turns out that has a large impact on how we program and design systems. But what if we had functions that couldn't fail and could run forever? It might sound like magic, but it's not. It's durable execution, and it's a huge DX improvement in reliable backend programming. Find more info about All Things Open: On the web: https://www.allthingsopen.org/ Twitter: https://twitter.com/AllThingsOpen LinkedIn: https://www.linkedin.com/company/all-things-open/ Instagram: https://www.instagram.com/allthingsopen/ Facebook: https://www.facebook.com/AllThingsOpen Mastodon: https://mastodon.social/@allthingsopen Threads: https://www.threads.net/@allthingsopen 2023 conference: https://2023.allthingsopen.org/
System Design on Easy Mode
- 1. System Design on Easy Mode All Things Open October 16th, 2023 Raleigh, North Carolina
- 2. - Developer relations engineer @ Temporal - Worked on Temporal’s JavaScript runtime - Wrote a book on GraphQL - Consultant & open-source maintainer 2 Loren Sands-Ramshaw
- 3. 04 System design patterns 03 How? 02 New possibilities 01 Durable execution Today’s Agenda 3
- 5. 5 Normal execution Functions fail to complete executing when: - Process crashes
- 6. 6 Normal execution Functions fail to complete executing when: - Process crashes - Process killed by OS
- 7. 7 Normal execution Functions fail to complete executing when: - Process crashes - Process killed by OS - Machine loses power
- 8. 8 Normal execution Functions fail to complete executing when: - Process crashes - Process killed by OS - Machine loses power - Deploy new code
- 9. 9 Normal execution Functions fail to complete executing when: - Process crashes - Process killed by OS - Machine loses power - Deploy new code - Transient failures
- 10. Functions are guaranteed to complete running 10 Durable execution
- 11. Functions are guaranteed to complete running 11 Durable execution
- 12. Functions are guaranteed to complete running 12 Durable execution Transient failures are automatically retried
- 13. Coding at a higher level of abstraction 13 Durable execution
- 14. Coding at a higher level of abstraction 14 Durable execution High-level languages Low-level languages
- 15. Coding at a higher level of abstraction 15 Durable execution High-level languages Low-level languages Durable code Normal code
- 17. New possibilities - await sleep('30 days') 17 Durable execution
- 18. 18 New possibilities - await sleep('30 days') - Send RPCs to the function Durable execution
- 19. 19 New possibilities - await sleep('30 days') - Send RPCs to the function - Forever functions Durable execution
- 20. 20 New possibilities - await sleep('30 days') - Send RPCs to the function - Forever functions - Don’t have to use a database Durable execution
- 21. 21 Subscription Handle an RPC Sleep for days
- 22. 22 Forever function Variable > database Runs forever
- 23. 23 - Process independent - Automatic retries - Sleep - RPCs - Forever functions - Local variables instead of database Durable execution
- 24. 24 - Process independent - Automatic retries - Sleep - RPCs - Forever functions - Local variables instead of database Durable execution … but how?
- 25. How? 03
- 27. 27 Forever function Variable > database Runs forever
- 29. 29 Used by
- 32. Circuit breakers Event-driven architecture 32 Design patterns
- 33. Design patterns: event-driven architecture 33
- 37. Circuit breakers Event-driven architecture Sagas Transactional outboxes 37 Design patterns
- 38. Design patterns: event-driven architecture 38
- 39. 39 Circuit breakers Event-driven architecture Sagas Transactional outboxes Event sourcing Design patterns
- 40. Design patterns: event sourcing 40
- 41. CQRS Circuit breakers Event-driven architecture Sagas Transactional outboxes Event sourcing 41 Design patterns
- 42. 42 Design patterns: CQRS (Command Query Responsibility Segregation)
- 43. CQRS Distributed cron jobs 43 Design patterns Circuit breakers Event-driven architecture Sagas Transactional outboxes Event sourcing
- 44. CQRS Distributed cron jobs Task queues 44 Design patterns Circuit breakers Event-driven architecture Sagas Transactional outboxes Event sourcing
- 45. CQRS Distributed cron jobs Task queues State machines 45 Design patterns Circuit breakers Event-driven architecture Sagas Transactional outboxes Event sourcing
- 46. CQRS Distributed cron jobs Task queues State machines Circuit breakers Event-driven architecture Sagas Transactional outboxes Event sourcing 46 Design patterns
- 47. Recap 47 04 System design patterns 03 How 02 New possibilities 01 Durable execution