Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Maestro: Netflix's Workflow Orchestrator

netflixtechblog.com

Post reply on HN
Print view View original

161–165 of 165 posts

Re: Maestro: Netflix's Workflow Orchestrator

#161

Post by IamLoading »

skissane wrote: post #68
halamadrid wrote: post #62

Earlier quoted context omitted.

Yes Netflix abandoned Conductor long time ago [0]. The other repo is built and managed by Orkes after Netflix abandoned it. [0] https://techcrunch.com/2023/12/13/orkes-forks-conductor-as-n...

I haven't touched Conductor for a few years now, but back in 2020 I did some work trying to implement it, even submitted a few PRs – https://github.com/Netflix/conductor/pulls?q=is%3Apr+author%... My impression of the code base, is I felt like it needed a lot of work to run in a non-Netflix environment. Which is part of why the project I was working on ended up abandoning Conductor – we were going to embed Conductor…

if you look at the linkedin history, the main 2 maintainers left around 6 months before they archived it.

Re: Maestro: Netflix's Workflow Orchestrator

#163

Post by nfkuler »

halamadrid wrote: post #62
skissane wrote: post #61

I'm a bit confused about what is going on here: This project appears to use Netflix/conductor [0]. But you go to that repo, you see it has been archived, with a message saying it is replaced by Netflix's internal non-OSS version, and by unmentioned community forks – by which I assume they mean Orkes Conductor [1]. But this isn't using Orkes Conductor, it looks like it is using the discontinued Netflix version `com.ne…

Yes Netflix abandoned Conductor long time ago [0]. The other repo is built and managed by Orkes after Netflix abandoned it. [0] https://techcrunch.com/2023/12/13/orkes-forks-conductor-as-n...

I can tell you coming from Netflix that we have not abandoned Conductor. In fact, we have more that 5x the usage of Conductor across the Company in the last 6 months alone. The news link above is a bit misleading.. We archived the project, and its now managed at conductor-oss/conductor project given that there are a few thousand companies using it and there are a few companies not managing this project and its now graduated to a new foundation, just like many projects before at Netflix (Iceberg for eg)

Re: Maestro: Netflix's Workflow Orchestrator

#164

Post by nfkuler »

swyx wrote: post #152
troebr wrote: post #18

Earlier quoted context omitted.

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 workfl…

former temporal employee here. netflix is very big, temporal-at-netflix always coexisted with other orchestration solutions including conductor > I think this is very much not-Temporal because it relies on a DSL instead of workflow as code. yup you get it. maestro defines things as json, which just inherently limits how you can write and test it with your normal app code

Again, another misleading comment here. Given the freedom and responsibility culture at Netflix. There is one team/person who has been using and promoting Temporal usage and all temporal conferences. Conductor is the main orchestration product at Netflix and will continue to be the case. We have increased the usage 5x in the last 6 months alone.

Re: Maestro: Netflix's Workflow Orchestrator

#165

Post by cbsmith »

bhawks wrote: post #103
cbsmith wrote: post #80

Earlier quoted context omitted.

> Please stop misusing accounting concepts. Assets can also be liabilities. The mortgages in a mortgage backed security is both an asset and a liability, as was only too well demonstrated in 2008... It's an asset in the security portfolio, but until you sell the security, it's a liability for whomever is securitizing it.

In the GFC the government literally created the Troubled _Asset_ Relief Program. Those MBSs were assets and didn't magically become liabilities. The problem was the market value of those assets plummeted because no one expected them to generate the agreed upon cash flows because the underlying loans were going into correlated defaults. Despite all this the only party that saw the mortgage as a liability is the indivi…

> Outside of swaps and other derivatives financial instruments and other properties don't magically switch from being an asset to being a liability based on random external factors.

I wasn't saying they switch; I'm saying they can be both an asset and a liability. Liability isn't strictly an accounting term. It also can refer to something that acts as a disadvantage. Illiquid assets whose valuation can be volatile can be a liability.

Post reply on HN