JLupin provides reactive queues with an option of automated retrieving results - of course in microservice architecture. Queues are defined on specific native microservices (queue microservices). The number of queues defined on the particular queue microservice as well as the number of queue microservices depends of your needs, processing characteristic, security rules and infrastructure resources. In that way you can build the queue subsystem in microservice architecture, where queues are separated by running its own JVMs. This way your queues will be more resistant to failures, outages, overloads, etc.

Figure 1. JLupin Reactive Queues Overview.

We recommend to define one queue per one queue microservice if the capacity of the infrastructure allows you to do it.

The most important thing is that JLupin Reactive Queues are the additional layer to your microservices that you don't need to implement, integrate or refer to in any way. They transparently covers your code providing high efficient reactive, asynchronous, distributed reactive bus.