Fallthrough Event Driven Architectures
19 snips
May 26, 2025 
Chris Richardson, a software architect and author of Microservice Patterns, joins Indu Alagarsamy, a principal engineer at the New York Times passionate about event-driven architectures, and Ignacio Castillejos, a staff software engineer in the subscription platform group. They dive into the world of event-driven architecture, discussing its benefits over traditional methods. Key topics include the importance of idempotency, the use of technologies like Kafka and GCP's Event Arc, and best practices for managing distributed systems. Real-world examples highlight the potential for scalability and reliability.
AI Snips
Chapters
Books
Transcript
Episode notes
Real-World Asynchronous Modeling
- Event-driven architecture models asynchronous, real-world events, avoiding procedural coupling seen in traditional synchronous calls.
- It enables decoupling, independent scaling, and better handling of latency and availability issues in distributed systems.
Leverage Messaging Frameworks
- Use established messaging frameworks like NServiceBus or MassTransit to handle retries, idempotence, and sagas.
- These platforms provide monitoring and tooling which simplify building reliable event-driven systems.
Ensure Reliability with Patterns
- Implement the transaction outbox pattern to atomically update business data and publish events reliably.
- Design message handlers to be idempotent to safely handle duplicate message deliveries.
