fabric8

32
93
+ 1
1
Istio

525
918
+ 1
40
Kong

382
898
+ 1
121
Advice on fabric8, Istio, and Kong
Needs advice
on
IstioIstioEnvoyEnvoy
and
AWS App MeshAWS App Mesh

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!

See more
Decisions about fabric8, Istio, and Kong
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 73.4K 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
Pros of fabric8
Pros of Istio
Pros of Kong

Sign up to add or upvote prosMake informed product decisions

Cons of fabric8
Cons of Istio
Cons of Kong
    No cons available
      No cons available

      Sign up to add or upvote consMake informed product decisions