S90-08 practice question 15 of 35

The Asynchronous Queuing pattern can be combined with the Event-Driven Messaging pattern to allow a service consumer acting as a subscriber to receive all event notification messages that are broadcast, even those that are sent when the service consumer is unavailable.

Full set: 100 questions
Answer options
A:

A. True

B:

B. False

Correct Answer:
TRUE
Explanation

The statement is correct. The Asynchronous Queuing pattern introduces an intermediary queue that stores messages, providing temporal decoupling between the message producer and consumer. When this is combined with the Event-Driven Messaging pattern (a publish-subscribe model), it creates a mechanism for durable subscriptions. The messaging system places a copy of each broadcast event notification into a dedicated, persistent queue for each subscriber. Consequently, if a subscriber is offline or unavailable when the event is published, the message is safely stored in its queue. When the subscriber comes back online, it can retrieve and process all the messages that accumulated during its downtime, ensuring no notifications are lost.

Why Incorrect

The alternative, "False," is incorrect because the primary benefit of introducing an asynchronous queue into a publish-subscribe architecture is to enhance reliability and availability. The queue's persistence mechanism is specifically designed to solve the problem of message loss when a consumer (subscriber) is temporarily unavailable, which is the exact scenario described in the question. This combination is a well-established compound pattern known as Durable Subscriber.

References

1. Erl, T. (2009). SOA Design Patterns. Prentice Hall.

Chapter 18: Compound Patterns, Durable Subscriber (p. 517): This section explicitly describes the compound pattern that combines Event-Driven Messaging and Asynchronous Queuing. It states, "By introducing an intermediary queue for each subscriber, messages can be temporarily persisted, waiting to be retrieved by the subscriber when it becomes available again... This allows the subscriber to go offline without losing any messages that may be published during its downtime."

Chapter 11: Messaging Patterns, Asynchronous Queuing (p. 287): The description of the base pattern highlights its core capability: "This pattern aims to avoid forcing the consumer to retrieve a message at the same time it is delivered by the producer... a temporary storage area is used to hold the message." This directly supports the mechanism described in the question.

2. Hohpe, G., & Woolf, B. (2003). Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions. Addison-Wesley. (This text is foundational in distributed systems and messaging, frequently used in university courseware).

Chapter 5: Messaging Patterns, Durable Subscriber (p. 198): The pattern is defined to address the problem: "How can a subscriber avoid missing messages while it’s not active?" The solution described is to "Have the messaging system save messages for the inactive subscriber and deliver them when the subscriber reconnects." This is achieved by using a persistent queue for the subscriber's messages.

Scroll to Top