Cron jobs don’t scale well when you’re on Kubernetes or in distributed systems — you end up with duplicates, failures, and a mess. We built Schedo to solve this and much more: a cloud scheduler that just works, without extra complexity. It’s designed to handle scale and reliability without you having to juggle locks, queues, or overkill third-party tools.
I just don't see what doesn't "scale" exactly here. Been using k8s for 7 years, never had a problem that wasn't my own fault. Even for parallel processing, I feel like there's so many options and patterns to use because it depends on the task the job does.
Cron jobs don’t scale well when you’re on Kubernetes or in distributed systems — you end up with duplicates, failures, and a mess. We built Schedo to solve this and much more: a cloud scheduler that just works, without extra complexity. It’s designed to handle scale and reliability without you having to juggle locks, queues, or overkill third-party tools.
Are you saying cronjobs in Kubernetes doesn't scale well? Specifically this core resource here is what I'm wondering about: https://kubernetes.io/docs/concepts/workloads/controllers/cr...
I just don't see what doesn't "scale" exactly here. Been using k8s for 7 years, never had a problem that wasn't my own fault. Even for parallel processing, I feel like there's so many options and patterns to use because it depends on the task the job does.
[dead]