take a look at https://github.com/conductor-sdk/conductor-python which is easier and will not force you to write with specific framework.

how does it compare to DBOS?

how is it different from Conductor? https://github.com/conductor-oss/conductor

I haven't used Conductor, but quickly looking at the README, Conductor lets you define JSON workflows to orchestrate existing microservices. By contrast, DBOS helps you build highly reliable applications--it runs as a library inside your program and helps you build durable workflows that run alongside your code and are written in the same language.

Maestro is a domain specific implementation for ML and data pipelines that uses Conductor as its core

https://netflixtechblog.com/orchestrating-data-ml-workflows-...

https://github.com/Netflix/maestro/blob/main/maestro-engine/...

Conductor was moved here: https://github.com/conductor-oss/conductor Maestro uses conductor as its core.

https://github.com/Netflix/maestro/blob/main/maestro-engine/...

https://netflixtechblog.com/orchestrating-data-ml-workflows-...

This is not true. Looks like they needed some functionalities and just used a small part of conductor.

Conductor was moved here: https://github.com/conductor-oss/conductor

And it is supported! https://orkes-conductor.slack.com

This has been there for a while and is supported on all three clouds.

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

Your jobs page only has developer advocate role open, and the link just leads back to the top of the jobs page.

This is/was an awesome resource which helped me understand the basics of Linux installations, distributions. Used it to build really minimal distros.

We use Airflow at scale, I am kind of wondering why do we need something different to manage workflows. The advantage I see with Airflow is that its simple, BashOperator allows me to execute my code in any language that I have written and the DAG is very simple to understand and reason about. Not to mention the dependency management aspect of it.