Compiled Conversations Thinking in Events: Principles of Event-Driven Architecture, Part 1 with James Eastham
Jul 23, 2025
James Eastham, a developer advocate at Datadog and former AWS expert, dives into the essentials of event-driven architecture. He unpacks how communication shapes software design and discusses the pros and cons of different architectures like microservices. Key topics include the importance of semantically meaningful events, managing idempotency, and employing standards like CloudEvents. With vivid pizza metaphors, James illustrates concepts such as eventual consistency and balancing loose and strong coupling, making complex ideas accessible and engaging.
AI Snips
Chapters
Books
Transcript
Episode notes
Use Business Language In Events
- Event-driven means using the business's language in events, not implementation details.
- Consumers shouldn't need to know producers' internal technologies like S3.
Translate Technical Events Into Domain Events
- Keep technical events private and translate them into business-domain events for others.
- Only expose domain events to external consumers to avoid leaking implementation details.
Be Intentional With Thick vs Thin Events
- Choose thin (IDs only) or thick (entity state) events based on control over endpoints and ownership.
- Be conservative in what you send and intentional about added fields for external consumers.
