QuestionQ23

MuleSoft application network concepts

See the exhibits.

An Order microservice and a Fulfillment microservice are being designed to communicate with their clients through message-based integration, rather than API invocations.

The Order microservice publishes an Order message (a kind of command message) containing details of an order to be filled. The intent is for Order messages to be consumed by only one Mule application: the Fulfillment microservice.

The Fulfillment microservice consumes Order messages, fills the orders described in them, and then publishes a Fulfillment message (a kind 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 choice of message broker(s) and message destination(s) for this scenario?

Question Image

  • A
  • B
  • C
  • D
Explanation

A JMS point-to-point queue delivers each message to only one receiver, which fits an Order command intended solely for the Fulfillment microservice. A JMS publish-subscribe topic supports multiple consumers, which fits a Fulfillment event available to the Order microservice and any other interested applications. The shared queue and topic are hosted by the same JMS provider used by both microservices.

Learn more

Community Discussion

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