PEpetromir·Jul 30, 2024
So they abandoned https://github.com/Netflix/conductor to create Maestro
In Maestro: Netflix's Workflow OrchestratorNetflix
conductor
Java2016–2024
Netflix / conductor · Archived
conductor
Conductor is a microservices orchestration engine.
13Distinct people
23Mentions
1Explicit recommenders
12.8KGitHub stars
What to know before exploring
What it is
Conductor is a microservices orchestration engine.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
One of my favorite workflow engines that has a really simple way to do things was not listed here, so I'll call it out - Netflix Conductor…
jusonchan81 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year23 dated mentions
Observed mentions: 2016-12-22 14:29:15 UTC to 2024-07-30 13:46:38 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 8 | 3 | 5 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 6 | 4 | 2 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 4 | 0 | 4 |
What Hacker News says
23 sourcesI 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 in our product as a workflow engine, we ended up building our own workflow engine from scratch instead. Another team did end up using it for some internal use cases, but scalability/reliability/etc are less of a concern for internal use cases as opposed to customer-facing ones.
And then Netflix abandons it – and then they open source something else which depends on an old version of it – well, I'm happy they open source anythi
Read the rest
ng, but it fits with my earlier impression – throwing stuff over the fence which can be a struggle to adopt in an outside environment. Still, throwing it over the fence is better than not releasing it at all.
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.netflix.conductor:conductor-core:2.31.5` [2] – and an outdated version of it too.
[0] https://github.com/Netflix/conductor
[1] https://github.com/conductor-oss/conductor
[2] https://github.com/Netflix/maestro/blob/e8bee3f1625d3f31d84d...
In Maestro: Netflix's Workflow OrchestratorI 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.
In Netflix has open-sourced its Maestro Workflow OrchestratorNetflix Conductor OSS discontinued support
4 points · Open discussionOne of my favorite workflow engines that has a really simple way to do things was not listed here, so I'll call it out - Netflix Conductor (https://github.com/Netflix/conductor).
Its capabilities comes to light when you model really complex workflows and one real value is how its all very visual not just during modeling but when running it. The history remains visible and you can even see how the whole flow evolved.
In The Workflow PatternFramework used by Netflix to orchestrate microservices
1 points · Open discussionNetflix Conductor Version 3.13.7
4 points · Open discussionOrkes | Backed and Front-end Engineers | Full Time | Remote or Bay Area | https://orkes.io/careers/
Orkes offers cloud hosted version of Netflix Conductor (https://github.com/Netflix/conductor). We are the core developers and founders of Conductors prior to founding Orkes.
We are looking for engineers who are interested in building the platform used by many fortune 100 companies to build their distributed stateful applications.
In this role, you will constantly push the boundaries of what is possible in a distributed system and developer experience.
In Ask HN: Who is hiring? (June 2023)Yeah, that's quite interesting reading from them, some sort of specialized appliance really.
I'm and the average Joe around me, totally far from Netflix's task of packing bytes from disk to network. Simple 2vCPU VPS serving 4GBit without being saturated on system resource level is quite often much more than enough. Extra note - it's not even using kTLS.
Moreover, even for Netflix, noting they know FreeBSD in and out, do you think/have info on using FreeBSD as base OS beyond distribution level - running applications/services in particular?
I've quickly checked on their repos like https://github.com/Netflix/conductor and it smells like they use containers/Docker, which doesn't work on FreeBSD => I'm in very much doubts it's OS of choice for them.
In Dozens of malicious PyPI packages discovered targeting developersorkes.io | Customer Success Engineer / Solutions Architect | Remote | FTE
We are building the next generation of orchestration platform based on https://github.com/Netflix/conductor and are looking for folks who are passionate about making the users successful in their journey.
Talk to us jobs@orkes.io.
In Ask HN: Who is hiring? (August 2022)Orkes | Senior Software Engineers | Remote | Full Time | https://orkes.io/
Interested in solving the distributed systems challenges?
We are building the future of how developers build software across the world. Starting with a cloud hosted service on Netflix Conductor (https://github.com/Netflix/conductor).
We are looking for software engineers who are excited to go beyond building applications to building the platform on which application are built.
We are remote first, fully distributed team and well funded by VCs.
https://orkes.io/careers/
In Ask HN: Who is hiring? (May 2022)Show HN: Create Conductor Workflows Using Code
1 points · Open discussionShowing the 15 most recent of 23 sources. Enable JavaScript to search and browse every indexed mention.