mercredi 22 août 2018

Dynamic message "routing" pattern?

We are building an application using microservices and AWS SQS for messaging.

We have a requirement for a single message to be handled by multiple microservices before being processed at a "final destination" microservice.

For example:

  • microservice A generates a message
  • the message must be validated by microservice B
  • the validated message must be transformed using microservice C
  • the transformed message must be applied to a data store using microservice D

Is there a pattern for dynamically (at message-creation time) prescribing the flow of a message between listeners on a message queue?

Aucun commentaire:

Enregistrer un commentaire