Overview

fabric8

Stacks37

Followers113

Votes1

GitHub Stars1.8K

Forks498

Istio

Stacks2.3K

Followers1.5K

Votes54

GitHub Stars37.6K

Forks8.1K

Istio vs fabric8: What are the differences?

Control Plane: Istio primarily focuses on managing microservices traffic by providing a control plane that helps in implementing various traffic management techniques like load balancing, routing, and traffic shifting. On the other hand, fabric8 focuses on enhancing the development process by providing tools for building, testing, and deploying applications.
Supported Platforms: Istio is more tightly integrated with Kubernetes and is widely used in Kubernetes environments for managing microservices communication. Fabric8, on the other hand, provides support for a wider range of platforms beyond just Kubernetes, including OpenShift, Docker, and other container platforms.
Monitoring and Observability: Istio comes with built-in support for monitoring and observability features like distributed tracing, monitoring dashboards, and telemetry data collection. Fabric8 also offers monitoring capabilities, but it is more focused on developer experience and providing insights into the development lifecycle.
Service Mesh Implementation: Istio is known for its robust service mesh implementation that provides advanced features like mutual TLS authentication, fault injection, and circuit breaking for microservices. Fabric8, while offering some service mesh functionalities, is more oriented towards simplifying the development and deployment processes for applications.
Community Support: Istio has a strong community backing, with contributions and support from major tech companies like Google, IBM, and Lyft. Fabric8, as an open-source project under the Fabric8.io community, also has an active community support, but it is relatively smaller compared to Istio.
Customization and Extensibility: Istio provides a high level of customization and extensibility through its rich set of APIs, allowing users to tailor their microservices communication policies and configurations. Fabric8, while offering some level of customization, is more opinionated in its approach and provides predefined patterns and workflows for application development.

In Summary, Istio focuses on managing microservices traffic with a strong emphasis on Kubernetes environments, while fabric8 is more oriented towards enhancing the development experience across various platforms beyond just Kubernetes.

🔥 Trending in API Tools on StackShare

Postman

API Tools

Only complete API development environment

Try it View Docs Alternatives

Try

25

82.5k

Advice on fabric8, Istio

Prateek

Mar 14, 2020

Decided

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.

322k views322k

Comments

lyc218

Feb 21, 2020

Needs advice

Envoy proxy is widely adopted in many companies for service mesh proxy, but it utilizes BoringSSL by default. Red Hat OpenShift fork envoy branch with their own OpenSSL support, I wonder any other companies are also using envoy-openssl branch for compatibility? How about AWS App Mesh?

Any input would be much appreciated!

42.7k views42.7k

Comments

Detailed Comparison

fabric8	Istio
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.	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.
Statistics
GitHub Stars 1.8K	GitHub Stars 37.6K
GitHub Forks 498	GitHub Forks 8.1K
Stacks 37	Stacks 2.3K
Followers 113	Followers 1.5K
Votes 1	Votes 54
Pros & Cons
Pros 1 Easy to build and automate integration testing	Pros 14 Zero code for logging and monitoring 9 Service Mesh 8 Great flexibility 5 Powerful authorization mechanisms 5 Resiliency Cons 17 Performance
Integrations
Docker Kubernetes Jenkins	Kubernetes Docker

What are some alternatives to fabric8, Istio?

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.

Micro

Micro is a framework for cloud native development. Micro addresses the key requirements for building cloud native services. It leverages the microservices architecture pattern and provides a set of services which act as the building blocks