Thereās a new Streaming Audio episode - check it out!
Event-driven architecture has taken on numerous meanings over the yearsāfrom event notification to event-carried state transfer, to event sourcing, and CQRS. Why has event-driven programming become so popular, and why is it such a topic of interest?
For the first time, Simon Aubury (Principal Data Engineer, ThoughtWorks) joins Tim Berglund on the Streaming Audio podcast to tell all, including his own experiences adopting event-driven technologies and common blunders when working in this area.
Simon admits that heās made some mistakes and learned some valuable lessons that can benefit others. Among these are accidentally building a message bus, the idea that messages are not events, realizing that getting too fixated on the size of a microservice is the wrong problem, the importance of understanding events and boundaries, defining choreography vs. orchestration, and dealing with passive-aggressive events.
This brings Simon to where he is today, as he advocates for Apache KafkaĀ® as a foundation for building a scalable, event-driven architecture and data-intensive applications.
EPISODE LINKS
- Should You Put Several Event Types in the Same Kafka Topic?
- Meetup Recording: Event-Driven Architecture Mistakes ā Iāve Made a Few
- Join the Confluent Community
- Learn more with Kafka tutorials, resources, and guides at Confluent Developer
- Live demo: Kafka streaming in 10 minutes on Confluent Cloud
- Use 60PDCAST to get an additional $60 of free Confluent Cloud usage (details)
Listen to the episode