Getting started with Event-Driven APis
summary
Practical primer on turning request/response APIs into event-driven systems, showing concrete tooling and patterns: Kafka and Red Hat AMQ for messaging, schema registry for contracts, and an example microservice pair (publisher + consumer) wired to a topic. Demonstrates how to handle out‑of‑order delivery, consumer replay for backfill, and dead‑letter handling, and measures end‑to‑end tradeoffs in coupling and latency. Slides include code snippets, deployment steps, and troubleshooting tips that work against legacy systems.
AI-written summary · about
chapters (6)
- 0:00Event-driven APIs intro
- 4:51Event-driven architecture concepts
- 10:14Building event-driven apps
- 17:02Use cases and protocols
- 21:45Challenges and best practices
- 26:08Closing & Q&A
related talks
31mDemystifying Event-Driven Architectures
26mEvent Driven APIs
27mPatterns for Event-Driven APIs
41mGetting started with Event-Driven Architectures in 2023
42mCreating event-driven microservices: the why, how and what
52mSo You Want to Build An Event Driven System?
52mSo You Want to Build An Event Driven System?
32mUnifying API and event driven architectures
