Interview Bootcamp
Vote

0% completed

​

Messaging patterns

A messaging pattern is a standard way for components in a distributed system to communicate through asynchronous messages. Choosing the right pattern is a big part of designing a scalable and reliable system. This lesson covers the five patterns you will meet most often: point-to-point, publish-subscribe, request-reply, fan-out/fan-in, and the dead letter queue. For each one, we look at the core idea, how it works, and where it is used.

Point-to-Point (Direct Messaging)

In the point-to-point pattern, each message is delivered to exactly one consumer

.....

.....

.....

Like the course? Get enrolled and start learning!
A

Aniket Joshi

· 2 years ago

should this "

  • Coupling: The pattern can introduce tighter coupling between producers and consumers since the consumer must wait for a reply"

be changed to "producer must wait for a reply" ?

Show 1 reply
Sid D

Sid D

· a year ago

By the time a consumer picks a message from the queue, processes it and fails due to message corruption, the message is already out of the queue service isn’t it? Then how can the queue service move the message to the DLQ when the message is now with the consumer service? Does the consumer explicitly put it back into the queueing service?

Please provide more detailed examples of when, who and how messages are moved to DLQ

Aman Singh

Aman Singh

· 2 years ago

Under Request- Reply messaging pattern. it's written

Latency: Request-reply messaging can introduce latency as the consumer must wait for the reply to arrive.

Should it instead be producer must wait for the reply to arrive?

Show 1 reply
T

Tee Sal

· 2 years ago

"An order processing system where an order is placed by a customer producer"

Show 1 reply