REST the events: REST APIs for Event-Driven Architecture
summary
Compares synchronous request–response via HTTP with decoupled event streaming on Apache Kafka, arguing Java clients remain the lowest-latency path while HTTP wins for legacy apps, mobile and languages with poor Kafka clients. Describes concrete tools: Confluent REST Proxy (community‑licensed), Kafka Connect and CDC connectors (Oracle released recently), and a new Confluent Cloud REST API in early access to create connectors, manage users and environments. Notes real tradeoffs: easier ops and onboarding with HTTP versus higher scale, decoupling and “event thinking” costs when moving to full streaming.
AI-written summary · about
chapters (4)
related talks
26mREST the Events - REST APIs for Event-Driven Architecture
21mREST APIs vs. Data Streams: Which Is Right for Your Business?
27mOptimize Your API with Event-Driven Microservice Architecture.
26mEvent Driven APIs
29mAPIs and Event Streaming Dualty
38mAdvanced API Design for Scalable Distributed Systems
47mStream All the Things!
32mUnifying API and event driven architectures