AWS App Mesh vs Gubernator

Overview

AWS App Mesh

Stacks23

Followers205

Votes0

Gubernator

Stacks0

Followers11

Votes0

GitHub Stars960

Forks97

AWS App Mesh vs Gubernator: What are the differences?

What is AWS App Mesh? Easily monitor and control microservices running on AWS. 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.

What is Gubernator? A High Performance Rate Limiting MicroService and Library. It is a distributed, high performance, cloud native and stateless rate limiting service. It evenly distributes rate limit requests across the entire cluster, which means you can scale the system by simply adding more nodes.

AWS App Mesh and Gubernator can be categorized as "Microservices" tools.

Gubernator is an open source tool with 272 GitHub stars and 13 GitHub forks. Here's a link to Gubernator's open source repository on GitHub.

🔥 Trending in API Tools on StackShare

#1 Brand API - Brand.dev API Tools

#1 Brand API - Brand.dev

Try it View Docs Alternatives

Try

1

Advice on AWS App Mesh, Gubernator

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

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

AWS App Mesh	Gubernator
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.	It is a distributed, high performance, cloud native and stateless rate limiting service. It evenly distributes rate limit requests across the entire cluster, which means you can scale the system by simply adding more nodes.
-	provides both GRPC and HTTP access to it’s API; Can be run as a sidecar to services; Can be used as a library to implement a domain specific rate limiting service
Statistics
GitHub Stars -	GitHub Stars 960
GitHub Forks -	GitHub Forks 97
Stacks 23	Stacks 0
Followers 205	Followers 11
Votes 0	Votes 0
Integrations
Amazon EKS Amazon EC2 Kubernetes Envoy Amazon EC2 Container Service	Kubernetes Docker Compose

What are some alternatives to AWS App Mesh, Gubernator?

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.