Skip to content
This repository has been archived by the owner on Jul 7, 2022. It is now read-only.

Singleton message processing & queueing #1

Open
josh-endries opened this issue Apr 1, 2016 · 1 comment
Open

Singleton message processing & queueing #1

josh-endries opened this issue Apr 1, 2016 · 1 comment

Comments

@josh-endries
Copy link

Hello,

Thanks for this project, this seems exactly what Im looking for but I have a couple questions:

I don't know a whole lot about Redis pub-sub yet, I've used it mainly to store key-value data, but I believe that it publishes (at least by default) messages to all subscribers. If I want to use Redis for it's speed and reusability with other apps that might publish to it, but only have one continuous webjob process a message in a scaled-up set of webjob hosts, is that possible with this?

Also if no listeners are listening at the time, like maybe during an outage or restart, would the messages queue up in Redis until a webjob re-subscribes, or are they more ephemeral? I guess I'm wondering about how transactional is the usage.

Thanks again

@JasonHaley
Copy link
Owner

Good question. Let me do some research and find out.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants