Timeline for How to implement a message queue over Redis?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:01 | history | edited | CommunityBot | Commonmark migration | |
| Jun 11, 2016 at 2:32 | comment | added | djechlin | @raiglstorfer haven't worked there for two years :P feel free to research and post... | |
| Jun 10, 2016 at 22:26 | comment | added | ra9r | Agreed. How has this progressed? I like the idea of removing RabbitMQ from the stack and use Redis which is there anyway. My issue is how to register a consumer using RSMQ (node lib). | |
| Jan 13, 2015 at 10:02 | comment | added | bjornl | AAA: just like @AaronM I would love to hear how you have progressed. | |
| Apr 22, 2014 at 23:04 | comment | added | AaronM | I am curious as to how far you have come since last August. Were you able to solve your problems to your satisfaction? How did you solve them? | |
| Apr 22, 2014 at 23:03 | comment | added | AaronM | Not sure I follow the problem with blocking consumers. It seems to me that if there is no work to process consumers should block until there is some, though I suppose if the consumer is also doing other things that might be a different story, but isn't that more of an issue within the application and not so much for the queue? I.E. wouldnt a thread blocking within a larger app be a more elegant solution, where the thread would then be able to notify the app when it had retrieved a job from the queue. Perhaps it is just the use of node that is creating the complication. | |
| Aug 22, 2013 at 21:30 | history | edited | djechlin | CC BY-SA 3.0 | added 4 characters in body |
| Jul 15, 2013 at 16:13 | history | edited | djechlin | CC BY-SA 3.0 | added 302 characters in body |
| Jul 15, 2013 at 16:02 | history | answered | djechlin | CC BY-SA 3.0 |