Also, I made jam.
McSweeneys continues to be one of the best things ever.
Lamda does Scheduled Execution, but that's cron, not delayed execution.
SQS could almost be bent into shape with Message Visibility, but it would need something else on the end to handle cancellation. And there's a ceiling on the delay, five minutes I think.
But if I had to build this thing myself, that's might be how I'd do it, because I don't want to have to work with Quartz.
I want a cloudshit, Delayed Execution As A Service.
Invoke a function (Lambda or whatever) with payload X but it doesn't actually get run until after Y ms. Receive back an id Z, which can be used to cancel the execution if needed.
It's basically for an escalation system - unless an ACK is received after a few minutes, escalate alert to the next recipient. Right now there are workers polling to see if they need to do anything, which is sub-optimal.
Stupid idea - database migrations powered by git diff. All tables have to be defined as files in a repo as CREATE TABLE statements
To create migrations it runs `git diff master..`. Any new rows are added to the migration as `alter table add` statements. Any changed rows are alter column statements, etc. Such a dumb idea that I've already created the git repo for my joke implementation.
Sydney-based Technologist and learner. Chaotic Uncertain. Noted pineappleist. He. Him. His.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!