A microservices orchestration engine created by Netflix to manage workflows across distributed services.
Conductor is a microservices orchestration engine developed by Netflix to manage and coordinate workflows across distributed services. It solves the complexity of handling business processes that involve multiple microservices by providing a platform to define, execute, and monitor these workflows reliably. The engine supports both JSON and code-based workflow definitions, making it adaptable to various development environments.
Developers and engineering teams building microservices architectures who need to orchestrate complex workflows across distributed systems. It is particularly useful for organizations scaling their service-oriented infrastructure.
Developers choose Conductor for its battle-tested design from Netflix, extensible architecture with support for multiple persistence backends, and comprehensive SDKs for multiple languages. Its ability to handle scalable workflow orchestration with built-in system tasks and Docker deployment makes it a robust alternative to custom solutions.
Conductor is a microservices orchestration engine.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Developed and scaled by Netflix, Conductor is proven for robust workflow orchestration in large-scale production environments, as evidenced by its use in managing complex microservices.
Supports multiple backends like Redis, Cassandra, and Elasticsearch, allowing teams to choose storage solutions that fit their infrastructure needs, as detailed in the published artifacts.
Offers SDKs for various programming languages through conductor-sdk, enabling workflow creation in polyglot microservices ecosystems without being locked into Java.
Includes pre-built tasks for HTTP requests and JSON evaluation with jq, reducing custom code and accelerating development for common workflow operations.
Netflix discontinued maintenance in December 2023, leaving the project reliant on community forks, which may lack consistent updates, security patches, or professional support.
Requires Redis, Elasticsearch, JDK 17+, and Node 14 for the UI, adding significant setup and operational overhead compared to more lightweight or managed alternatives.
The server is built on Spring Boot, which can be a barrier for teams not invested in Java or Spring ecosystems, limiting flexibility in non-Java environments.