This appears to be the high level architecture: https://miro.medium.com/v2/resize:fit:4800/format:webp/0*SDt....
To me seems to overengineered for most of the companies outside there, how many people do you need to manage it?
To me seems to overengineered for most of the companies outside there, how many people do you need to manage it?
> … 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.
In other words, learn it now and get it on your resume, because within a year every 200-hit-per-day service and site is going to rearchitected to use it.