Adding an implementation of github.com/gobuffalo/buffalo/worker.Worker that uses Azure Service Bus to persist Jobs, distribute them between available machines, and provide Job status monitoring.
Reviewers, some open questions I still have:
Is github.com/Azure/buffalo-azure/worker a good package name for this? Would github.com/Azure/buffalo-azure/sdk/worker be better? I'm leaning towards the latter.
Is tying together the notion of Queue as its defined in worker.Job and a Service Bus Queue, as I've done here, appropriate?
For ServiceBusPublisher, should I add a "DefaultQueue" that will override which overrides the empty string if that's what's present in a Job?
How is the documentation I've added here? Any other examples I should add?
Is it clear why I broke up my implementation of the Worker interface into two halves?
Adding an implementation of
github.com/gobuffalo/buffalo/worker.Workerthat uses Azure Service Bus to persist Jobs, distribute them between available machines, and provide Job status monitoring.Reviewers, some open questions I still have:
github.com/Azure/buffalo-azure/workera good package name for this? Wouldgithub.com/Azure/buffalo-azure/sdk/workerbe better? I'm leaning towards the latter.Queueas its defined inworker.Joband a Service Bus Queue, as I've done here, appropriate?ServiceBusPublisher, should I add a "DefaultQueue" that will override which overrides the empty string if that's what's present in a Job?Workerinterface into two halves?@arschles @markbates