Need advice about which tool to choose?Ask the StackShare community!

Conductor

61
107
+ 1
0
Kong

576
1.4K
+ 1
135
Add tool

Conductor vs Kong: What are the differences?

Developers describe Conductor as "A microservices orchestration engine that runs in the cloud *". Conductor is an orchestration engine that runs in the cloud. On the other hand, *Kong** is detailed as "Open Source Microservice & API Management Layer". 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.

Conductor and Kong can be categorized as "Microservices" tools.

Some of the features offered by Conductor are:

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

On the other hand, Kong provides the following key features:

  • Logging: Log requests and responses to your system over TCP, UDP or to disk
  • OAuth2.0: Add easily an OAuth2.0 authentication to your APIs
  • Monitoring: Live monitoring provides key load and performance server metrics

Conductor and Kong are both open source tools. Kong with 22.4K GitHub stars and 2.75K forks on GitHub appears to be more popular than Conductor with 1.9K GitHub stars and 571 GitHub forks.

Decisions about Conductor and Kong
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 228.4K views

Istio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn-keyIstio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn key solution with Rancher whereas Kong completely lacks here. Traffic distribution in Istio can be done via canary, a/b, shadowing, HTTP headers, ACL, whitelist whereas in Kong it's limited to canary, ACL, blue-green, proxy caching. Istio has amazing community support which is visible via Github stars or releases when comparing both.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Conductor
Pros of Kong
    Be the first to leave a pro
    • 37
      Easy to maintain
    • 32
      Easy to install
    • 25
      Flexible
    • 20
      Great performance
    • 5
      Api blueprint
    • 4
      Custom Plugins
    • 3
      Kubernetes-native
    • 2
      Security
    • 2
      Agnostic
    • 2
      Has a good plugin infrastructure
    • 1
      Documentation is clear
    • 1
      Very customizable
    • 1
      Load balancing

    Sign up to add or upvote prosMake informed product decisions

    - No public GitHub repository available -

    What is Conductor?

    Conductor is an orchestration engine that runs in the cloud.

    What is Kong?

    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.

    Need advice about which tool to choose?Ask the StackShare community!

    Jobs that mention Conductor and Kong as a desired skillset
    CBRE
    United Kingdom of Great Britain and Northern Ireland England Birmingham
    CBRE
    United Kingdom of Great Britain and Northern Ireland England London
    CBRE
    United States of America Texas Houston
    What companies use Conductor?
    What companies use Kong?
    See which teams inside your own company are using Conductor or Kong.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Conductor?
    What tools integrate with Kong?
      No integrations found

      Sign up to get full access to all the tool integrationsMake informed product decisions

      Blog Posts

      GitHubPythonNode.js+26
      29
      15662
      What are some alternatives to Conductor and Kong?
      Composer
      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
      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.
      Zuul
      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.
      Jersey
      It is open source, production quality, framework for developing RESTful Web Services in Java that provides support for JAX-RS APIs and serves as a JAX-RS (JSR 311 & JSR 339) Reference Implementation. It provides it’s own API that extend the JAX-RS toolkit with additional features and utilities to further simplify RESTful service and client development.
      linkerd
      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.
      See all alternatives