In the blog, it claims: > … schedule hundreds of thousands of workflows, millions of jobs every day and operate with a strict SLO of less than 1 minute of sche

In the blog, it claims: > … schedule hundreds of thousands of workflows, millions of jobs every day and operate with a strict SLO of less than 1 minute of scheduler introduced delay even when there are spikes in the traffic. I wouldn’t necessarily call it over engineered if it can handle this type of workload. But if you are running a fraction of these workloads with a much more relaxed SLO (service level objection), then yea this is overengineered. Like any solution from FAANG, or “big tech”. It works for _them_ at scale but for 90% of companies the sheer management of this service will quickly outweigh the benefits.