Now, we have fully reactive microservices, both in terms of non-blocking synchronous REST APIs and event-driven asynchronous services. Let's try them out!
Three different configurations are prepared as follows, each in a separate Docker Compose file:
- Using RabbitMQ without the use of partitions
- Using RabbitMQ with two partitions per topic
- Using Kafka with two partitions per topic
However, before testing these three configurations, we first need to simplify testing of the reactive microservice landscape. Once simplified, we can proceed with testing the microservices.
So accordingly, the following two features need to be checked:
- Saving events for later inspection when using RabbitMQ
- A health API that can be used to monitor the state of the landscape
