Kuma vs fabric8

Overview

fabric8

Stacks37

Followers113

Votes1

GitHub Stars1.8K

Forks498

Kuma

Stacks16

Followers95

Votes0

GitHub Stars2.3K

Forks169

Kuma vs fabric8: What are the differences?

Deployment Approach: One key difference between Kuma and fabric8 is their deployment approach. Kuma focuses on simplifying and abstracting service mesh deployment for users, making it easier to manage and scale microservices. On the other hand, fabric8 offers a more comprehensive platform that includes not only service mesh capabilities but also tools for continuous integration and continuous delivery.
Traffic Routing: Another significant difference is in how they handle traffic routing. Kuma provides advanced traffic routing features, including traffic splitting and mirroring, to fine-tune how traffic flows through the service mesh. In contrast, fabric8 offers more basic traffic routing capabilities, focusing more on facilitating developer productivity and collaboration.
Built-in Observability: Kuma comes with built-in observability features, such as tracing and monitoring, to help users gain insights into the behavior of their microservices. In comparison, fabric8 provides basic observability tools but also integrates with external monitoring and logging systems for more comprehensive observability.
Community Support: The level of community support differs between Kuma and fabric8. Kuma is supported by a dedicated community that focuses on developing and improving the service mesh platform. On the other hand, fabric8 has a larger community that contributes to the overall development of the platform, including its CI/CD capabilities.
Integration Ecosystem: Kuma has a strong focus on integrating with various platforms and tools to provide a seamless experience for users. This includes integrations with popular cloud providers, Kubernetes distributions, and monitoring systems. In contrast, fabric8 offers a more standalone experience, with fewer integrations out of the box.
Performance Optimization: Kuma puts a strong emphasis on performance optimization, providing features like load balancing and circuit breaking to ensure high availability and reliability of microservices. Fabric8, while also prioritizing performance, may not offer the same level of optimization features as Kuma in certain scenarios.

In Summary, Kuma and fabric8 differ in their deployment approach, traffic routing capabilities, built-in observability, community support, integration ecosystem, and performance optimization.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on fabric8, Kuma

Mohammed

CTO at Famcare

Jan 16, 2020

Needs advice

One of our applications is currently migrating to AWS, and we need to make a decision between using AWS API Gateway with AWS App Mesh, or Kong API Gateway with Kuma.

Some people advise us to benefit from AWS managed services, while others raise the vendor lock issue. So, I need your advice on that, and if there is any other important factor rather than vendor locking that I must take into consideration.

38.8k views38.8k

Comments

Detailed Comparison

fabric8	Kuma
fabric8 makes it easy to create microservices, build, test and deploy them via Continuous Delivery pipelines then run and manage them with Continuous Improvement and ChatOps.	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.
-	Universal Control Plane; Lightweight Data Plane; Automatic; Multi-Tenancy; Network Security; Traffic Segmentation: With flexible ACL rules
Statistics
GitHub Stars 1.8K	GitHub Stars 2.3K
GitHub Forks 498	GitHub Forks 169
Stacks 37	Stacks 16
Followers 113	Followers 95
Votes 1	Votes 0
Pros & Cons
Pros 1 Easy to build and automate integration testing	No community feedback yet
Integrations
Docker Kubernetes Jenkins	YAML CentOS Kubernetes PostgreSQL Red Hat Enterprise Linux (RHEL) macOS Debian Ubuntu

What are some alternatives to fabric8, Kuma?

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.

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.

Moleculer

It is a fault tolerant framework. It has built-in load balancer, circuit breaker, retries, timeout and bulkhead features. It is open source and free of charge project.

Express Gateway

A cloud-native microservices gateway completely configurable and extensible through JavaScript/Node.js built for ALL platforms and languages. Enterprise features are FREE thanks to the power of 3K+ ExpressJS battle hardened modules.

ArangoDB Foxx

It is a JavaScript framework for writing data-centric HTTP microservices that run directly inside of ArangoDB.

Dapr

It is a portable, event-driven runtime that makes it easy for developers to build resilient, stateless and stateful microservices that run on the cloud and edge and embraces the diversity of languages and developer frameworks.

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.

Ocelot

It is aimed at people using .NET running a micro services / service oriented architecture that need a unified point of entry into their system. However it will work with anything that speaks HTTP and run on any platform that ASP.NET Core supports. It manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service.

Related Comparisons

Kuma vs fabric8: What are the differences?

Deployment Approach: One key difference between Kuma and fabric8 is their deployment approach. Kuma focuses on simplifying and abstracting service mesh deployment for users, making it easier to manage and scale microservices. On the other hand, fabric8 offers a more comprehensive platform that includes not only service mesh capabilities but also tools for continuous integration and continuous delivery.
Traffic Routing: Another significant difference is in how they handle traffic routing. Kuma provides advanced traffic routing features, including traffic splitting and mirroring, to fine-tune how traffic flows through the service mesh. In contrast, fabric8 offers more basic traffic routing capabilities, focusing more on facilitating developer productivity and collaboration.
Built-in Observability: Kuma comes with built-in observability features, such as tracing and monitoring, to help users gain insights into the behavior of their microservices. In comparison, fabric8 provides basic observability tools but also integrates with external monitoring and logging systems for more comprehensive observability.
Community Support: The level of community support differs between Kuma and fabric8. Kuma is supported by a dedicated community that focuses on developing and improving the service mesh platform. On the other hand, fabric8 has a larger community that contributes to the overall development of the platform, including its CI/CD capabilities.
Integration Ecosystem: Kuma has a strong focus on integrating with various platforms and tools to provide a seamless experience for users. This includes integrations with popular cloud providers, Kubernetes distributions, and monitoring systems. In contrast, fabric8 offers a more standalone experience, with fewer integrations out of the box.
Performance Optimization: Kuma puts a strong emphasis on performance optimization, providing features like load balancing and circuit breaking to ensure high availability and reliability of microservices. Fabric8, while also prioritizing performance, may not offer the same level of optimization features as Kuma in certain scenarios.

In Summary, Kuma and fabric8 differ in their deployment approach, traffic routing capabilities, built-in observability, community support, integration ecosystem, and performance optimization.

Kuma vs fabric8

Overview