Our usecase is we need to schedule and run many one-off jobs/activities.
The activity is going out and hitting an API and being able to report some metrics about that call. Fairly simple, but we may have many millions of these jobs waiting to happen (scheduled) or executing.
i.e. I schedule something to run at 6:00 pm tomorrow and this activity will never run again. It’s not chronic, but scheduled. Might be scheduled months in advance.
EDIT: For additional information, the requests are more or less “the same” (differences in the URL, but otherwise not too much). So we could theoretically run off a database that pulls the information off at execution time. (Reducing code for activities.)