3 ms·
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 ty
by pshirshov 2y ago
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?
It would be way too ambitious to call this thing an orchestrator, it seems to be just a primitive distributed DAG executor.
- pests 2y agoDid you miss the sections on how this allows cyclic graphs and not just DAG? It's hard to take your comment seriously when this was one of the earliest talking points.
- pshirshov 2y ago> In Maestro, a workflow is a DAG (Directed acyclic graph) of individual units of job definition called Steps.
- pests 2y agoThe link was changed at some point, from the original Medium article: > Unlike traditional workflow orchestrators that only support Directed Acyclic Graphs (DAGs), Maestro supports both acyclic and cyclic workflows and also includes multiple reusable patterns, including foreach loops, subworkflow, and conditional branch, etc. https://netflixtechblog.com/maestro-netflixs-workflow-orchestrator-ee13a06f9c78 https://netflixtechblog.com/maestro-netflixs-workflow-orches...