Following the Data: A Deeper Look into Distributed Applications
summary
Cloud-native systems move from monoliths to microservices and then to polyglot, CQRS-style architectures, but the hard numbers are latency and throughput: replication lag and event bandwidth drive correctness problems more than design purity. Practical tactics covered include using Kafka or durable event logs, partitioning by tenant or key, single-consumer partitions for ordering, idempotent keys to avoid retries, and versioned event schemas; beware the cost and complexity of event sourcing, CQRS, and exactly-once semantics.
AI-written summary · about
chapters (4)
- 0:00Introduction and background
- 7:48From monoliths to microservices
- 17:57Event sourcing and consistency challenges
- 27:58Key takeaways and Q&A
related talks
23mDesigning Robust and Scalable Distributed Applications
51mPatterns & Practices of Implementing Event-driven MicroSvc...
29mCloud Native Patterns – Shifting Responsibilities
47mTackling Cloud Complexity - Recipes From Real World Projects
51mStreaming Platforms in Event-Driven Systems: Patterns, Pitfalls, and Performance
02h 18mDistributed Systems: In the Daily Life of the Data Engineer
46mMicroservices Data Patterns: CQRS & Event Sourcing
13mLow-Maintenance Backend Architectures for Scalable Applications