complex scheduler solution ideas please

0

What is a scalable solution for running lambda at specific times in the future?

We are building a SaaS platform, in which our users can request a task to happen according a recurring schedule (simple parameter of {"frequency": "NNN minutes"}. They can also edit/delete this schedule, to affect that future events. There will be K's of users, requesting M's of tasks over time (from 1 min to 1 year). The tasks will not be created in the order they should execute. I need high integrity on completion.

I've discounted just using sqs. I've looked at cloudwatch events, but have concerns about scaling. I've considered putting the tasks into a DB table then polling. Is there something else I should look at?

2 Antworten
2
profile pictureAWS
beantwortet vor einem Jahr
  • yep, looks like thats it. We're giving it a run now. Thanks for your help

0
Akzeptierte Antwort

What are you scaling concerns with cloudwatch? Have you also considered EventBridge or Step Functions to create a workflow? Also why have you discontinued sqs?

Cloud_G
beantwortet vor einem Jahr
  • discounted SQS on its own, because there's no time/schedule attribute, all tasks are just FIFO... previously thought that cloudwatch events (where each future job is a scheduled task) would become expensive (millions of jobs). Now thinking that the recurring schedule of jobs is the item i create (likely in eventbridge), and that handles the creation of individual jobs/lambda calls

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen