This appears to be the high level architecture: <a href="https://miro.medium.com/v2/resize:fit:4800/format:webp/0*SDt718rSvgh2Nclv" rel="nofollow">https://miro.medium.com/v2/resize:fit:4800/format:webp/0*SDt...</a>.<p>To me seems to overengineered for most of the companies outside there, how many people do you need to manage it?
1) Scheduling seems to be primitive? (strategy: sequential)
2) That's seems to be just a DAG executor? No high-level frontend?
3) No executiun context?
4) No typings?
5) No concept of a stream?<p>It would be way too ambitious to call this thing an orchestrator, it seems to be just a primitive distributed DAG executor.
[dupe]<p>More discussion on official post: <a href="https://news.ycombinator.com/item?id=41037745">https://news.ycombinator.com/item?id=41037745</a>
I was hoping to try this out, but it doesn't build on my mac :/<p>Here's their tech blog post about it: <a href="https://netflixtechblog.com/orchestrating-data-ml-workflows-at-scale-with-netflix-maestro-aaa2b41b800c" rel="nofollow">https://netflixtechblog.com/orchestrating-data-ml-workflows-...</a>
I was just thinking didn't Netflix already have its own workflow engine: <a href="https://github.com/Netflix/conductor">https://github.com/Netflix/conductor</a>, but found out it's archived/EOL so this makes more sense now.
An abstraction on top of Conductor:
<a href="https://github.com/Netflix/maestro/blob/main/maestro-engine/src/main/java/com/netflix/conductor/core/execution/MaestroWorkflowExecutor.java">https://github.com/Netflix/maestro/blob/main/maestro-engine/...</a>