January 2019
Intermediate to advanced
520 pages
14h 32m
English
Very often, confusion is caused by asynchronous applications being called reactive, because their event loops wait for external events and don't waste server resources while they're waiting. Reactive microservices don't waste resources to keep incoming connection to return a result, because when a client connects to a reactive microservices for a short time, put the task and disconnects. After a client waits for asynchronous response from a microservice. Reactive microservices don't need to be asynchronous, but they can be.
When you choose message passing for interaction, you have to take into account that microservices have to be asynchronous and can handle multiple messages simultaneously. ...
Read now
Unlock full access