Alternatives to Kuma logo

Alternatives to Kuma

Panda, Istio, Envoy, Kong, and Zuul are the most popular alternatives and competitors to Kuma.
8
67
+ 1
0

What is Kuma and what are its top alternatives?

It is a universal open source control-plane for Service Mesh and Microservices that can run and be operated natively across both Kubernetes and VM environments, in order to be easily adopted by every team in the organization.
Kuma is a tool in the Microservices Tools category of a tech stack.
Kuma is an open source tool with 2.3K GitHub stars and 169 GitHub forks. Here’s a link to Kuma's open source repository on GitHub

Top Alternatives to Kuma

  • Panda

    Panda

    Panda is a cloud-based platform that provides video and audio encoding infrastructure. It features lightning fast encoding, and broad support for a huge number of video and audio codecs. You can upload to Panda either from your own web application using our REST API, or by utilizing our easy to use web interface.<br> ...

  • Istio

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

  • Envoy

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

  • Kong

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

  • Zuul

    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

    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

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

  • Azure Service Fabric

    Azure Service Fabric

    Azure Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable microservices. Service Fabric addresses the significant challenges in developing and managing cloud apps. ...

Kuma alternatives & related posts

Panda logo

Panda

8
19
0
Dedicated video encoding in the cloud
8
19
+ 1
0
PROS OF PANDA
    Be the first to leave a pro
    CONS OF PANDA
      Be the first to leave a con

      related Panda posts

      Istio logo

      Istio

      648
      1.1K
      42
      Open platform to connect, manage, and secure microservices, by Google, IBM, and Lyft
      648
      1.1K
      + 1
      42
      PROS OF ISTIO
      • 12
        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
      CONS OF ISTIO
      • 11
        Performance

      related Istio posts

      Anas MOKDAD
      Shared insights
      on
      KongKongIstioIstio

      As for the new support of service mesh pattern by Kong, I wonder how does it compare to Istio?

      See more
      Envoy logo

      Envoy

      235
      418
      8
      C++ front/service proxy
      235
      418
      + 1
      8
      PROS OF ENVOY
      • 8
        GRPC-Web
      CONS OF ENVOY
        Be the first to leave a con

        related Envoy posts

        Joseph Irving
        DevOps Engineer at uSwitch · | 7 upvotes · 128.5K views
        Shared insights
        on
        KubernetesKubernetesEnvoyEnvoyGoGo
        at

        At uSwitch we wanted a way to load balance between our multiple Kubernetes clusters in AWS to give us added redundancy. We already had ingresses defined for all our applications so we wanted to build on top of that, instead of creating a new system that would require our various teams to change code/config etc.

        Envoy seemed to tick a lot of boxes:

        • Loadbalancing capabilities right out of the box: health checks, circuit breaking, retries etc.
        • Tracing and prometheus metrics support
        • Lightweight
        • Good community support

        This was all good but what really sold us was the api that supported dynamic configuration. This would allow us to dynamically configure envoy to route to ingresses and clusters as they were created or destroyed.

        To do this we built a tool called Yggdrasil using their Go sdk. Yggdrasil effectively just creates envoy configuration from Kubernetes ingress objects, so you point Yggdrasil at your kube clusters, it generates config from the ingresses and then envoy can loadbalance between your clusters for you. This is all done dynamically so as soon as new ingress is created the envoy nodes get updated with the new config. Importantly this all worked with what we already had, no need to create new config for every application, we just put this on top of it.

        See more
        Shared insights
        on
        EnvoyEnvoyHAProxyHAProxyTraefikTraefikNGINXNGINX

        We are looking to configure a load balancer with some admin UI. We are currently struggling to decide between NGINX, Traefik, HAProxy, and Envoy. We will use a load balancer in a containerized environment and the load balancer should flexible and easy to reload without changes in case containers are scaled up.

        See more
        Kong logo

        Kong

        473
        1.1K
        130
        Open Source Microservice & API Management Layer
        473
        1.1K
        + 1
        130
        PROS OF KONG
        • 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
        CONS OF KONG
          Be the first to leave a con

          related Kong posts

          Al Tsang
          Problem/Challenge

          We needed a lightweight and completely customizable #microservices #gateway to be able to generate #JWT and introspect #OAuth2 tokens as well. The #gateway was going to front all #APIs for our single page web app as well as externalized #APIs for our partners.

          Contenders

          We looked at Tyk Cloud and Kong. Kong's plugins are all Lua based and its core is NGINX and OpenResty. Although it's open source, it's not the greatest platform to be able to customize. On top of that enterprise features are paid and expensive. Tyk is Go and the nomenclature used within Tyk like "sessions" was bizarre, and again enterprise features were paid.

          Decision

          We ultimately decided to roll our own using ExpressJS into Express Gateway because the use case for using ExpressJS as an #API #gateway was tried and true, in fact - all the enterprise features that the other two charge for #OAuth2 introspection etc were freely available within ExpressJS middleware.

          Outcome

          We opened source Express Gateway with a core set of plugins and the community started writing their own and could quickly do so by rolling lots of ExpressJS middleware into Express Gateway

          See more
          Anas MOKDAD
          Shared insights
          on
          KongKongIstioIstio

          As for the new support of service mesh pattern by Kong, I wonder how does it compare to Istio?

          See more
          Zuul logo

          Zuul

          159
          295
          6
          An edge service that provides dynamic routing, monitoring, resiliency, security, and more
          159
          295
          + 1
          6
          PROS OF ZUUL
          • 6
            Load blancing
          CONS OF ZUUL
            Be the first to leave a con

            related Zuul posts

            linkerd logo

            linkerd

            104
            244
            7
            Twitter-Style Operability for Microservices
            104
            244
            + 1
            7
            PROS OF LINKERD
            • 3
              CNCF Project
            • 1
              Fast Integration
            • 1
              Pre-check permissions
            • 1
              Light Weight
            • 1
              Service Mesh
            CONS OF LINKERD
              Be the first to leave a con

              related linkerd posts

              Jersey logo

              Jersey

              100
              97
              5
              A REST framework that provides a JAX-RS implementation
              100
              97
              + 1
              5
              PROS OF JERSEY
              • 3
                Lightweight
              • 1
                Fast Performance With Microservices
              • 1
                Java standard
              CONS OF JERSEY
                Be the first to leave a con

                related Jersey posts

                Azure Service Fabric logo

                Azure Service Fabric

                88
                231
                25
                Distributed systems platform that simplifies build, package, deploy, and management of scalable microservices apps
                88
                231
                + 1
                25
                PROS OF AZURE SERVICE FABRIC
                • 5
                  Intelligent, fast, reliable
                • 3
                  Open source
                • 3
                  Superior programming models
                • 3
                  More reliable than Kubernetes
                • 3
                  Runs most of Azure core services
                • 3
                  Reliability
                • 2
                  Quickest recovery and healing in the world
                • 1
                  Deploy anywhere
                • 1
                  Is data storage technology
                • 1
                  Battle hardened in Azure > 10 Years
                CONS OF AZURE SERVICE FABRIC
                  Be the first to leave a con

                  related Azure Service Fabric posts