Asynchornous Request-Reply Pattern
Decouple backend processing from a frontend host, where backend processing needs to be asynchronous, but the frontend still needs a clear response.
Choreography Pattern
Have each component of the system participate in the decision-making process about the workflow of a business transaction, instead of relying on a central point of control.
Competing Consumers Pattern
Enable multiple concurrent consumers to process messages received on the same messaging channel.
Priority Queue Pattern
Prioritize requests sent to services so that requests with a higher priority are received and processed more quickly than those with a lower priority.
Publisher-Subscriber Pattern
Enable an application to announce events to multiple interested consumers asynchronously, without coupling the senders to the receivers.
Saga Pattern
Manage data consistency across microservices in distributed transaction scenarios. A saga is a sequence of transactions that updates each service and publishes a message or event to trigger the next transaction step.