Very nice, Netflix has a reputation of making great OSS products. I wonder where does this stand with Conductor.
[deleted]
Maestro: Netflix's Workflow Orchestrator
11–20 of 165 posts
Re: Maestro: Netflix's Workflow Orchestrator
#12The name Maestro has already been used for a workflow orchestrator which I worked on back in 2016. That maestro is SQL-centric and infers dependencies automatically by simply examining the SQL. It's written in Go and is BigQuery-specific (but could be easily adjusted to use any SQL-based system).
Re: Maestro: Netflix's Workflow Orchestrator
#13why would one consider this over something more established such as Temporal, also I see Maestro is written in Java vs Temporal's Go
That's also my question.
Re: Maestro: Netflix's Workflow Orchestrator
#14Don't see many Java projects being posted on HN.
Re: Maestro: Netflix's Workflow Orchestrator
#15Seems like they re-engineered Temporal: https://temporal.io/
Re: Maestro: Netflix's Workflow Orchestrator
#16Don't see many Java projects being posted on HN.
We only upvote Go or Rust projects here ;)
Re: Maestro: Netflix's Workflow Orchestrator
#17I wonder how many iterations we will need before engineers are happy with a workflow solution. Netflix had multiple solutions before Maestro, such as metaflow. Uber built multiple solutions too. Amazon had at least a dozen internal workflow engines. It's quite curious why engineers are so keen on building their own workflow engines.
Update: I just find it really interesting that many individuals in many companies like to build workflow engines. This is a not deriding comment towards anyone or Netflix in particular. To me, such observation is worth some friendly chitchat.
Re: Maestro: Netflix's Workflow Orchestrator
#18Seems like they re-engineered Temporal: https://temporal.io/
They did use Temporal at Netflix, they gave a couple presentations 2 years ago. I think this is very much not-Temporal because it relies on a DSL instead of workflow as code.
I don't know if it's a scale-thing, I'm not a workflow expert but this seems more in line with the map-reduce of yore, as in you get some big fat steps and you coordinate them, although you could have coarse-grained activities in Temporal workflows.
I'd be curious to see what the tradeoffs are between the two and if they still have usages for Temporal. Maybe Maestro is better for less technical people? Latency? Scale?
Re: Maestro: Netflix's Workflow Orchestrator
#19why would one consider this over something more established such as Temporal, also I see Maestro is written in Java vs Temporal's Go
Netflix also uses temporal: https://temporal.io/in-use/netflix
Re: Maestro: Netflix's Workflow Orchestrator
#20[flagged]