Core message patterns: one message/two services (continued)

1/2: Winner-take-all

If the message is asynchronous, then no immediate reply is expected. The sending microservice simply does not care what happens after the message is emitted. In this case, the message is consumed, meaning that it is delivered to at most one listening microservice. A work queue can be used as the message transport mechanism to implement this pattern.

Example: Resizing images with a set of workhorse machines.

1/2: Fire-and-forget

The purest microservice communication ...

Get The Tao of Microservices now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.