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

Kong

530
1.3K
+ 1
128
OpenResty

2.3K
212
+ 1
0
Add tool
Decisions about Kong and OpenResty
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 187.7K 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 Kong
Pros of OpenResty
  • 36
    Easy to maintain
  • 31
    Easy to install
  • 24
    Flexible
  • 20
    Great performance
  • 5
    Api blueprint
  • 4
    Custom Plugins
  • 3
    Kubernetes-native
  • 2
    Agnostic
  • 1
    Security
  • 1
    Documentation is clear
  • 1
    Load balancing
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    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.

    What is OpenResty?

    OpenResty (aka. ngx_openresty) is a full-fledged web application server by bundling the standard Nginx core, lots of 3rd-party Nginx modules, as well as most of their external dependencies.

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

    Jobs that mention Kong and OpenResty as a desired skillset
    What companies use Kong?
    What companies use OpenResty?
    See which teams inside your own company are using Kong or OpenResty.
    Sign up for StackShare EnterpriseLearn More

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

    What tools integrate with Kong?
    What tools integrate with OpenResty?

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

    Blog Posts

    GitHubDockerReact+17
    35
    32605
    GitHubPythonNode.js+26
    29
    15526
    What are some alternatives to Kong and OpenResty?
    Apigee
    API management, design, analytics, and security are at the heart of modern digital architecture. The Apigee intelligent API platform is a complete solution for moving business to the digital world.
    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.
    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.
    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.
    See all alternatives