The Rise of Reactive Microservices
summary
Argues that microservices move from synchronous calls to event-centric persistence and push‑based streams (Kafka, Pulsar, CDC via Kafka Connect), with concrete patterns: publish user and transaction events, build local projections (hydrated read models) and scale by sharding (by country/user group) plus Kafka Streams or Flink for processing. Gives numbers and tradeoffs: 93% of mobile banking use cases are balance/transactions, eventual consistency splits into divergence/variance/latency and is mitigated by partition ordering, idempotency/dedup, and optimistic UIs.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:43Microservices and reactive programming
- 6:16Reactive programming with streams
- 11:15Synchronous microservices challenges
- 15:31Message-driven microservices resilience
- 18:21Entity service anti-pattern and DDD
- 23:58Reactive data streams for autonomy
- 32:59Eventual consistency trade-offs
- 35:47Banking architecture with reactive microservices
- 41:42Sharded stream-based scalability
- 43:47Microservices evolution and costs
- 44:27Summary
- 44:47Q&A
related talks
37mBeyond Microservices: Streams, State & Scalability
27mOptimize Your API with Event-Driven Microservice Architecture.
11mLightning Talk: Event Based Communication in Complex Micro-service...
48mReactive Microservice in Action
48mChallenges in Implementing MicroServices
47mEvent-Driven Microservices = Microservices Done Right
50mAddressing Recent Events
49mMicroservices guided by DDD and reactive systems paradigm
