Live data from Hacker News

Netflix has open-sourced its Maestro Workflow Orchestrator

github.com

11–20 of 42 posts

Re: Netflix has open-sourced its Maestro Workflow Orchestrator

#11
post #4
post #3

I was hoping to try this out, but it doesn't build on my mac :/ Here's their tech blog post about it: https://netflixtechblog.com/orchestrating-data-ml-workflows-...

[flagged]

Not sure about the others but java is just an issue, if the devs did not care about cross platform and is mostly easy to fix if native libraries are absent.

Re: Netflix has open-sourced its Maestro Workflow Orchestrator

#13
post #2

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?

That chart has real Krazam Microservices vibes to it.

Re: Netflix has open-sourced its Maestro Workflow Orchestrator

#16
post #3

I was hoping to try this out, but it doesn't build on my mac :/ Here's their tech blog post about it: https://netflixtechblog.com/orchestrating-data-ml-workflows-...

It doesn't build on windows either. It looks to be missing some dependency.

       > Did not resolve 'com.github.vmg.protogen:protogen-annotations:1.0.0' which is part of the dependency lock state

Re: Netflix has open-sourced its Maestro Workflow Orchestrator

#17
post #6
post #2

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?

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),…

Over-engineering is in the eye of the beholder

Re: Netflix has open-sourced its Maestro Workflow Orchestrator

#18
post #6
post #2

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?

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),…

> 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.

Re: Netflix has open-sourced its Maestro Workflow Orchestrator

#20
post #3

I was hoping to try this out, but it doesn't build on my mac :/ Here's their tech blog post about it: https://netflixtechblog.com/orchestrating-data-ml-workflows-...

I've been able to build and run it sucessfully via IntelliJ, on an M2 Air.

Takes a few mins to get all the dependencies and build, but it definitely works.

Perhaps you're missing some dependency steps before hand if you're hand cranking gradle.

Post reply on HN