What is Conductor?
Conductor is an orchestration engine that runs in the cloud.
Conductor is a tool in the Microservices Tools category of a tech stack.
Conductor is an open source tool with 3.8K GitHub stars and 1.2K GitHub forks. Here’s a link to Conductor's open source repository on GitHub
Who uses Conductor?
47 developers on StackShare have stated that they use Conductor.
- Allow creating complex process / business flows in which individual task is implemented by a microservice.
- A JSON DSL based blueprint defines the execution flow.
- Provide visibility and traceability into the these process flows.
- Expose control semantics around pause, resume, restart, etc allowing for better devops experience.
- Allow greater reuse of existing microservices providing an easier path for onboarding.
- User interface to visualize the process flows.
- Ability to synchronously process all the tasks when needed.
- Ability to scale millions of concurrently running process flows.
- Backed by a queuing service abstracted from the clients.
- Be able to operate on HTTP or other transports e.g. gRPC.
Conductor Alternatives & Comparisons
What are some alternatives to Conductor?
See all alternatives
It is a tool for dependency management in PHP. It allows you to declare the libraries your project depends on and it will manage (install/update) them for you.
Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio's control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes, Mesos, etc.
Kong is a scalable, open source API Layer (also known as an API Gateway, or API Middleware). Kong controls layer 4 and 7 traffic and is extended through Plugins, which provide extra functionality and services beyond the core platform.
It is the front door for all requests from devices and websites to the backend of the Netflix streaming application. As an edge service application, It is built to enable dynamic routing, monitoring, resiliency, and security. Routing is an integral part of a microservice architecture.
linkerd is an out-of-process network stack for microservices. It functions as a transparent RPC proxy, handling everything needed to make inter-service RPC safe and sane--including load-balancing, service discovery, instrumentation, and routing.