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.
Netflix has open-sourced its Maestro Workflow Orchestrator
21–30 of 42 posts
Re: Netflix has open-sourced its Maestro Workflow Orchestrator
#22Re: Netflix has open-sourced its Maestro Workflow Orchestrator
#23This 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
#24I 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
#25So, is this something like prefect, dagster, flyte..?
Re: Netflix has open-sourced its Maestro Workflow Orchestrator
#26It would be way too ambitious to call this thing an orchestrator, it seems to be just a primitive distributed DAG executor.
Re: Netflix has open-sourced its Maestro Workflow Orchestrator
#27Re: Netflix has open-sourced its Maestro Workflow Orchestrator
#28I was just thinking didn't Netflix already have its own workflow engine: https://github.com/Netflix/conductor , but found out it's archived/EOL so this makes more sense now.