<https://dev.to/kumo/a-serverless-solution-to-just...
# sstj
JP (junaway)
06/17/2022, 6:12 PMhttps://dev.to/kumo/a-serverless-solution-to-just-in-time-scheduling-3cn6 this could be a quick add to the list of constructs.
t
thdxr
06/17/2022, 6:33 PMfrank was recently talking about implementing something like this with sfns
thdxr
06/17/2022, 6:33 PMbut I imagine this maybe is cheaper?
j
JP (junaway)
06/17/2022, 6:37 PMThere is a blog somewhere where they argue that this is the cheapest and most precise (serverless) option currently available on AWS.
JP (junaway)
06/17/2022, 6:40 PMI used to have a home-made, minute-level precision service like that and I'd hook it to everything : from interservice hooks/callbacks to mobile messages (through mqqt/websocket or Google/FCM).
It's one of the missing pieces in serverless 😅
a
Akos
06/17/2022, 6:42 PMYeah, agreed that it's missing piece on AWS. Having something like this in SST would be great 👍
Akos
06/17/2022, 6:42 PMThere are these three articles that cover the same topic:
• https://theburningmonk.com/2019/03/dynamodb-ttl-as-an-ad-hoc-scheduling-mechanism/
• https://theburningmonk.com/2019/05/using-cloudwatch-and-lambda-to-implement-ad-hoc-scheduling/
• https://theburningmonk.com/2019/06/step-functions-as-an-ad-hoc-scheduling-mechanism/
j
JP (junaway)
06/17/2022, 6:54 PMUnfortunately TTL is not reliable (minutes or hours of jitter) and cloudwatch and step functions aren't cheap and you still need a lambda.
t
Timothée Clain
06/17/2022, 6:59 PM+1 for step functions. super easy to setup with cdk, we use it for our notification engine
2 Views