News for hackers. Stuff that matters.
Re:Replacing cron jobs with a centralized task scheduler by danielheath on Friday August 01, 2025 @04:14AM (#44754200)
Depends what else you’re running on it; it’s a little expensive, but not prohibitively so.
Re:Replacing cron jobs with a centralized task scheduler by maxbond on Friday August 01, 2025 @05:17AM (#44754578)
Long running transactions interfere with vacuuming and increase contention for locks. Everything depends on your workload but a long running transactions holding an important lock is an easy way to bring down production.
Re:Replacing cron jobs with a centralized task scheduler by iglio on Friday August 01, 2025 @06:07AM (#44754833)
If the system is already using SQS, DynamoDB has this locking library which is lighter weight for this use case

https://github.com/awslabs/amazon-dynamodb-lock-client

> The AmazonDynamoDBLockClient is a general purpose distributed locking library built on top of DynamoDB. It supports both coarse-grained and fine-grained locking.