4 ms·

This appears to be the high level architecture: https://miro.medium.com/v2/resize:fit:4800/format:webp/0*SDt718rSvgh2Nclv https://miro.medium.com/v2/resize:fit:

This appears to be the high level architecture: https://miro.medium.com/v2/resize:fit:4800/format:webp/0*SDt718rSvgh2Nclv 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?

xyst 2y ago
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.
- galaxyLogic 2y ago
  Over-engineering is in the eye of the beholder
- silisili 2y ago
  > 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.
nrclark 2y ago
That chart has real Krazam Microservices vibes to it.
- darknavi 2y ago
  > First we call Bingo to get our Name-o.
  - earthboundkid 2y ago
    Love Galactus.
- alex_lav 2y ago
  All time great Youtube video. Still heavily relevant today.
- rubslopes 2y ago
  Here's a video of Primeagen, a YouTuber who uses to be a dev at Netflix, watching that video and then telling a very similar story that happened at Netflix: https://youtu.be/s-vJcOfrvi0 https://youtu.be/s-vJcOfrvi0
  - rjbwork 2y ago
    Brilliant. Currently dealing with webs of microservices myself. It's truly wild to watch something akin to the cambrian explosion with these things.
apwell23 2y ago
this looks like someone took their systems design interview too seriously

xyst 2y ago

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.

galaxyLogic 2y ago
Over-engineering is in the eye of the beholder
silisili 2y ago
> 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.

nrclark 2y ago

That chart has real Krazam Microservices vibes to it.

darknavi 2y ago
> First we call Bingo to get our Name-o.
- earthboundkid 2y ago
  Love Galactus.
alex_lav 2y ago
All time great Youtube video. Still heavily relevant today.
rubslopes 2y ago
Here's a video of Primeagen, a YouTuber who uses to be a dev at Netflix, watching that video and then telling a very similar story that happened at Netflix: https://youtu.be/s-vJcOfrvi0 https://youtu.be/s-vJcOfrvi0
- rjbwork 2y ago
  Brilliant. Currently dealing with webs of microservices myself. It's truly wild to watch something akin to the cambrian explosion with these things.

apwell23 2y ago

this looks like someone took their systems design interview too seriously