Communication and Transactionality in Distributed Systems
summary
An engineer from MacPaw describes how their team transformed a monolithic platform into a distributed system, detailing step-by-step architectural decisions for component decoupling and the challenges encountered. The talk covers approaches to improving transaction management, coordination and communication between services, stability and performance optimizations, and lessons learned from experiments and failures.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:53Websites to distributed systems
- 7:28Monolith to microservices
- 10:13BFF benefits
- 13:42Splitting monolith challenges
- 16:13Event streaming vs REST
- 18:20Saga pattern for transactionality
- 23:22Orchestration vs choreography
- 27:58Saga orchestration with Temporal
- 31:29Q&A
- 33:12REST and Saga workflows
- 36:48Async responses and tracking
- 38:34Alerting in Sagas
- 39:36Microservices vs monolith profit
- 42:02Team structure in microservices
- 43:06Why use BFF
related talks
50mCommunication in a Distributed World
01h 00mChallenges of distributed systems
01h 03mMicroservices vs The Distributed Monolith
37mHow to manage complexity in distributed applications
01h 02mConsistency and Agreements in Distributed Systems
11mScaling systems, scaling influence: Lessons from distributed architecture
34mThe Road to a Distributed Application, or the Pitfalls of CQRS/DDD
23mDesigning Robust and Scalable Distributed Applications