You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 7, 2022. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: