In the following scenarios, a purely reactive approach is a perfect fit:
- When most of the processing in your application can be done asynchronously. When you can have parallel processing in your application, the reactive architecture pattern is a great fit for processing application needs.
- Decentralizing the application flow in each service is manageable and it doesn't become a pain in the neck. For monitoring and auditing, centralized views can be generated using correlation IDs (UUID, GUID, CUID).
- When the application needs to be deployed quickly and speed to market is a top-most goal. When microservices are combined with a reactive approach, it helps to increase decoupling, minimize dependencies, ...