Reactive Microservice in Action
summary
Explains what “reactive” actually fixes: nonblocking I/O, unknown consumers, and slow or failing downstreams. Shows use of CompletionStage, MicroProfile Fault Tolerance (timeout, circuit breaker, fallback), MicroProfile Reactive Messaging plus Reactive Streams semantics and back pressure. Demonstrates two microservices: a producer generating random prices, a consumer subscribed to a Kafka topic on IBM Cloud (TLS auth); messages flow through the topic and the consumer processes them successfully, proving decoupling and resilience.
AI-written summary · about
chapters (17)
- 0:00Reactive Microservices in Action
- 2:39Two microservices...
- 3:57Interacting using synchronous calls
- 5:04Asynchronous calls (because it's trendy)
- 7:01Microservices are like kids...
- 8:08Micro Profile Fault-Tolerance
- 10:19Sorry, I'm out of context...
- 11:37Micro Profile Context Propagation
- 17:45Reactive all the things ???
- 19:08Reactive Programming
- 19:38Reactive Extensions
- 23:53Reactive Streams - Java 9. edition
- 29:30Applying reactive to microservices
- 30:42Reactive Systems
- 32:37Using messages to achieve decoupling
- 33:24MicroProfile Reactive Messaging
- 36:13Reactive architecture
related talks
30mReactive Microservices
50mBuilding reactive microservices with MicroProfile
47mThe Rise of Reactive Microservices
54mReacting to an Event-Driven World
24mBringing Reactive Programming to Java and Microservices
50mAddressing Recent Events
53mRefactor to Reactive with Spring 5 and Project Reactor
01h 01mThirst Quenching Streams for the Reactive Mind