I am experiencing a project where a microservice sends asynchronous message to itself via RabbitMQ, because it contains both the message producer and consumer parts. The reason is that the service can then produce the same type messages to the other services and receive the same type message from the other services.
This pattern is new to me. Is it anti-pattern in the microservice world?
Aucun commentaire:
Enregistrer un commentaire