Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Disque – a distributed message broker

github.com

Post reply on HN
Print view View original

21–30 of 96 posts

Re: Disque – a distributed message broker

#21

Post by dsugarman »

uptown wrote: post #18

Can somebody help me better understand the possible uses for something like this?

as a communication layer between modules or micro services or any distributed system. if you want to push global updates to a system, you can push a message out to a channel and all of the subscribers will get the message.

Re: Disque – a distributed message broker

#22

Post by antirez »

uptown wrote: post #18

Can somebody help me better understand the possible uses for something like this?

Let's say you have a web app that sends emails, and you have many worker processes actually sending emails. If you use something like Disque, instead of sending the email directly from the web app, you send a message to Disque, into the send_email queue: "Please send an email to foo@example.com". Workers sending emails will fetch from the send_email queue, and will get the message. Workers sending emails are supposed to acknowledged to Disque when they were actually able to process the message, so if they fail in some way, the message is re-queued and delivered again to the same or another worker, after a time you specify. So basically it adds a reliable middle-layer between the different moving parts of your application. The user will receive its email, or during failures it may receive the email multiple times, but it can never happen that no email is received by the user, since Disque guarantees that the message will be removed only once acknowledged.

Re: Disque – a distributed message broker

#23

Post by uptown »

dsugarman wrote: post #21
uptown wrote: post #18

Can somebody help me better understand the possible uses for something like this?

as a communication layer between modules or micro services or any distributed system. if you want to push global updates to a system, you can push a message out to a channel and all of the subscribers will get the message.

Clarifies it perfectly for me. Thanks for the response.

Re: Disque – a distributed message broker

#25

Post by counterplex »

spoiler wrote: post #15
damon_c wrote: post #10

Are people pronouncing this word like "Diskqueue"?

I've assumed it's a phonetic play, and that it's pronounced "dis queue" as in "this queue."

That's close. It's meant to be more like dysfunctional queue.

From the README:

DIStributed QUEue but is also a joke with "dis" as negation (like in disorder) of the strict concept of queue, since Disque is not able to guarantee the strict ordering you expect from something called queue. And because of this tradeof it gains many other interesting things.

Post reply on HN