// the find
Netflix/conductor
Conductor is a microservices orchestration engine.
Conductor is Netflix's workflow orchestration engine for coordinating long-running processes across microservices. It defines workflows as JSON (or code via SDK) with tasks executed by workers that poll a central server. Netflix officially abandoned it in December 2023 and handed it to the community.
Battle-tested at Netflix scale before abandonment — the core orchestration model (task polling, workflow state machine, external payload storage) is genuinely well-designed. Multiple persistence backends (Redis, Cassandra) and queue implementations (SQS) are pluggable via Spring autoconfiguration, not hardcoded. The Java SDK supports defining workflows in code rather than raw JSON, which makes versioning and refactoring tractable. gRPC and REST interfaces coexist, so you're not locked into one transport.
Officially dead as of December 2023 — Netflix stopped all maintenance, which means no security patches, no JDK compatibility fixes, no bug fixes on the original repo. The community forks (Orkes, conductor-oss) are real alternatives but you're now betting on a third party's roadmap, not Netflix's. Default persistence is Redis + Elasticsearch 6.x, which is an end-of-life version of ES — running this in production today means you're immediately dealing with unsupported dependencies. The polling-based worker model adds latency and puts constant load on the server; if you're building something new, event-driven alternatives like Temporal handle this better.