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

Singleton message processing & queueing #1

@josh-endries

Description

@josh-endries

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions