Istio vs Kong vs Spring Cloud

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

Istio

663
1.2K
+ 1
44
Kong

481
1.2K
+ 1
130
Spring Cloud

698
637
+ 1
0
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Istio
Pros of Kong
Pros of Spring Cloud
  • 13
    Zero code for logging and monitoring
  • 8
    Service Mesh
  • 7
    Great flexibility
  • 4
    Ingress controller
  • 3
    Resiliency
  • 3
    Easy integration with Kubernetes and Docker
  • 3
    Full Security
  • 3
    Powerful authorization mechanisms
  • 36
    Easy to maintain
  • 30
    Easy to install
  • 24
    Flexible
  • 20
    Great performance
  • 5
    Api blueprint
  • 4
    Custom Plugins
  • 3
    Kubernetes-native
  • 2
    Agnostic
  • 1
    Documentation is clear
  • 1
    1
  • 1
    123123
  • 1
    12312312
  • 1
    123
  • 1
    12
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Cons of Istio
    Cons of Kong
    Cons of Spring Cloud
    • 13
      Performance
      Be the first to leave a con
        Be the first to leave a con

        Sign up to add or upvote consMake informed product decisions

        - No public GitHub repository available -
        - No public GitHub repository available -

        What is 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.

        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 Spring Cloud?

        It provides tools for developers to quickly build some of the common patterns in distributed systems.

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

        What companies use Istio?
        What companies use Kong?
        What companies use Spring Cloud?

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

        What tools integrate with Istio?
        What tools integrate with Kong?
        What tools integrate with Spring Cloud?

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

        Blog Posts

        GitHubPythonNode.js+26
        28
        15369
        What are some alternatives to Istio, Kong, and Spring Cloud?
        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.
        Envoy
        Originally built at Lyft, Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and “universal data plane” designed for large microservice “service mesh” architectures.
        Kubernetes
        Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
        Conduit
        Conduit is a lightweight open source service mesh designed for performance, power, and ease of use when running applications on Kubernetes. Conduit is incredibly fast, lightweight, fundamentally secure, and easy to get started with.
        AWS App Mesh
        AWS App Mesh is a service mesh based on the Envoy proxy that makes it easy to monitor and control containerized microservices. App Mesh standardizes how your microservices communicate, giving you end-to-end visibility and helping to ensure high-availability for your applications. App Mesh gives you consistent visibility and network traffic controls for every microservice in an application. You can use App Mesh with Amazon ECS (using the Amazon EC2 launch type), Amazon EKS, and Kubernetes on AWS.
        See all alternatives