Netflix Conductor: Open-source workflow orchestration engine

Re:Netflix Conductor: Open-source workflow orchestration engine by dap on Wednesday August 19, 2020 @09:39PM (#24218994)

Thanks for the resources! It seems like a lot of these implementations expect to run as independently managed services in some microservice architecture. Are you aware of any workflow engines implemented as a library inside your application, maybe with storage backed by an external database? I think that you could still have a highly available model, provided the database supported that.

[ Parent | on HN ]

Re:Netflix Conductor: Open-source workflow orchestration engine by hukola on Thursday August 20, 2020 @08:36AM (#24222562)

https://github.com/ing-bank/baker is one such library for JVM languages. The state is kept in Cassandra or in-memory. We've been running production workloads with it for the last 2.5 years. A feature comparison with alternatives can be found here https://ing-bank.github.io/baker/sections/feature-comparison....

[ Parent | on HN ]

Re:Netflix Conductor: Open-source workflow orchestration engine by mianos on Thursday August 20, 2020 @06:20AM (#24221738)

Prefect. It's a workflow engine in a python library.

[ Parent | on HN ]

Re:Netflix Conductor: Open-source workflow orchestration engine by manyxcxi on Wednesday August 19, 2020 @10:31PM (#24219281)

Funny, even though Conductor isn’t designed to be- this is exactly how we use it. In a Kotlin and Spring Boot codebase nonetheless!

[ Parent | on HN ]

Re:Netflix Conductor: Open-source workflow orchestration engine by AlphaSite on Thursday August 20, 2020 @03:35AM (#24220813)

Like celery?

[ Parent | on HN ]