rasmusw on Fri, 03 Jul 2015 07:45:40
I'm a bit confused regarding the job limitations of the Azure Scheduler.
I am in need of a scheduler that can potentially manage 100,000 trigger times. The jobs to be triggered are very similar. Basically they are an event message with a few parameters.
The trigger times are not recurring, but are one-off events. For example scheduled alarm triggering for a large number of alarms.
With the premium scheduler it's possible to have 10,000 job collections with 50 jobs in each, and scale up the number of units. That could work, but seems expensive, and difficult to have to manage placing the jobs into job collections and units manually.
The Quartz scheduler has a notion of a Job which can be triggered at many times with different parameters. Since the jobs I need scheduled are so similar, I could do with only one job, that has with two parameters: Start/Stop and an ID.
Do I really need to schedule new jobs with the Azure scheduler for run trigger time, or is it similar to the Quartz scheduler's Job/Trigger notion?