Optimize Your API with Event-Driven Microservice Architecture.

on YouTube ↗27m

" summary

Argues replacing long chains of synchronous REST calls with an event-driven backbone using Kafka and connectors, claiming 10x–20x throughput gains in customer migrations and enabling real-time enrichment, stateful materialized views and replay for ML. Notes limits: single-digit millisecond latency (not nanoseconds), and a real case where 30 dependent sync calls drop overall availability to 99.7%. Recommends Kafka + ksqlDB + Kafka Streams for processing, databases for indexed queries, and the Saga pattern for compensation to handle eventual consistency.

AI-written summary · about

" chapters (9)

1. 0:00Event-driven microservices intro
2. 1:04Why event-driven is necessary
3. 7:12Event-driven vs synchronous APIs
4. 14:44When to avoid event-driven
5. 17:15Exposing APIs externally
6. 20:06Databases in event-driven systems
7. 23:02Handling eventual consistency
8. 25:09Preventing infinite loops
9. 25:51Closing remarks

" related talks

• 42mCreating event-driven microservices: the why, how and whatKatherine Stanley · Voxxed Days Microservices 2019
• 47mThe Rise of Reactive MicroservicesDavid Leitner · Craft Conference 2022
• 37mBeyond Microservices: Streams, State & ScalabilityGwen Shapira · GOTO Chicago 2020
• 01h 08mEvent Driven Architecture – Enabling MicroservicesBrad Irby · Silicon Valley Code Camp 2018
• 59mBuilding Data Intensive Microservices with Apache KafkaYaniv Rodenski · NDC Sydney 2017
• 26mMetamorphosis: Microservices & Event-driven ArchitectureAlianna Inzana · apidays Paris 2021
• 47mEvent-Driven Microservices = Microservices Done RightUrs Peter · J-Fall 2022
• 21mHow Apache Kafka® Generates Value In Retail With ConfluentAnna Semjen · Big Data LDN 2022