This document discusses reactive microservices and introduces key reactive concepts like asynchronous communication, back pressure, and context propagation. It describes how MicroProfile specifications like Reactive Messaging, Fault Tolerance, and Context Propagation enable building reactive systems. Reactive systems use asynchronous messaging to achieve temporal decoupling between services. This improves elasticity, resilience and allows services to use non-blocking I/O to efficiently use resources. The document provides code samples and references to demonstrate developing reactive microservices.
Convert to study materialsBETA
Transform any presentation into ready-made study materialselect from outputs like summaries, definitions, and practice questions.
1 of 41
Download to read offline
More Related Content
Reactive microserviceinaction
1. Reactive Microservices In Action
Emily Jiang
Java Champion
STSM, IBM
Liberty Microservice Architect, Advocate
MicroProfile Architect @IBM
@emilyfhjiang
40. References
Defining the term reactive
https://developer.ibm.com/articles/defining-the-term-reactive/
Develop reactive microservices with Reactive Messaging
https://developer.ibm.com/articles/develop-reactive-microservices-with-
microprofile/
Open Liberty guides on Reactive
https://openliberty.io/guides/?search=reactive
MicroProfile Reactive Messaging
https://github.com/eclipse/microprofile-reactive-messaging
MicroProfile Fault Tolerance
https://github.com/eclipse/microprofile-fault-tolerance/
MicroProfile Context Propagation
https://github.com/eclipse/microprofile-context-propagation
41. Thank you
41
Emily Jiang
STSM, Liberty Microservice Architect and Advocate
IBM
@emilyfhjiang
Dr. Clement Escoffier
Senior Principal Software Engineer
Red Hat
@clementplop