QuestionQ59

VerifiedDesigning architecture using integration paradigms

Refer to the exhibits.

Question Image

An Order microservice and a Fulfillment microservice are being designed to communicate with their clients using message-based integration (and not API invocations).

The Order microservice publishes an Order message (a type of command message) that contains the details of an order to be fulfilled. The intention is for Order messages to be consumed by only one Mule application: the Fulfillment microservice.

The Fulfillment microservice consumes Order messages, fulfills the orders they describe, and then publishes a Fulfillment message (a type of event message). Any interested Mule application can consume each Fulfillment message, and the Order microservice is one such Mule application.

What is the recommended selection of message broker(s) and message destination(s) for this scenario?

Explanation

A JMS queue implements point-to-point messaging, in which only one consumer receives a message, making it appropriate for Order command messages intended solely for the Fulfillment microservice. A JMS topic implements publish-subscribe messaging, allowing multiple interested consumers to receive Fulfillment event messages. Both destinations can be provided by the same JMS broker instance, sized for the combined workload.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!