AWS App Mesh vs linkerd

Overview

linkerd

Stacks132

Followers312

Votes7

AWS App Mesh

Stacks23

Followers205

Votes0

AWS App Mesh vs linkerd: What are the differences?

Introduction

In this markdown, we will be discussing the key differences between AWS App Mesh and linkerd.

Service Mesh Type:

AWS App Mesh is a fully managed service mesh offered by Amazon Web Services (AWS).
On the other hand, linkerd is an open-source service mesh for cloud-native applications.

Supporting platforms:

AWS App Mesh is primarily designed to work with AWS services, making it a suitable choice for applications deployed on the AWS ecosystem.
In contrast, linkerd is platform-agnostic and can be used with various cloud providers and on-premises environments.

Managed vs. Self-hosted:

AWS App Mesh is a fully managed service, which means that all the operational aspects of the service are managed by AWS.
In contrast, linkerd is a self-hosted service mesh where the user is responsible for the deployment and management of the service mesh.

Integration with Other Tools:

AWS App Mesh integrates seamlessly with other AWS services, such as Amazon Elastic Compute Cloud (EC2), Amazon Elastic Kubernetes Service (EKS), and AWS Fargate.
On the other hand, linkerd can work with any container orchestrator, including Kubernetes.

Traffic Management Capabilities:

AWS App Mesh provides advanced traffic management capabilities, including built-in support for implementing traffic routing and load balancing policies.
In contrast, linkerd offers basic traffic management functionalities but also provides powerful observability features like telemetry and distributed tracing.

Pricing Model:

AWS App Mesh pricing is based on the resources used, such as the number of service meshes, virtual routes, and virtual nodes.
Linkerd, being an open-source service mesh, is free to use without any licensing costs.

In summary, AWS App Mesh is a fully managed service mesh primarily designed for the AWS ecosystem, whereas linkerd is an open-source platform-agnostic service mesh with self-hosted deployment. AWS App Mesh provides robust integration with AWS services and advanced traffic management capabilities, while linkerd offers basic traffic management functionalities with powerful observability features without any licensing costs.

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 linkerd, AWS App Mesh

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

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.8k views42.8k

Comments

Detailed Comparison

linkerd	AWS App Mesh
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.	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.
Adaptive load-balancing;Fine-grained instrumentation;Abstractions over service discovery;Runtime traffic routing;Tech that's built for scale	-
Statistics
Stacks 132	Stacks 23
Followers 312	Followers 205
Votes 7	Votes 0
Pros & Cons
Pros 3 CNCF Project 1 Service Mesh 1 Light Weight 1 Pre-check permissions 1 Fast Integration	No community feedback yet
Integrations
No integrations available	Amazon EKS Amazon EC2 Kubernetes Envoy Amazon EC2 Container Service

What are some alternatives to linkerd, AWS App Mesh?

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.

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

Related Comparisons

AWS App Mesh vs linkerd: What are the differences?

Introduction

In this markdown, we will be discussing the key differences between AWS App Mesh and linkerd.

Service Mesh Type:

AWS App Mesh is a fully managed service mesh offered by Amazon Web Services (AWS).
On the other hand, linkerd is an open-source service mesh for cloud-native applications.

Supporting platforms:

AWS App Mesh is primarily designed to work with AWS services, making it a suitable choice for applications deployed on the AWS ecosystem.
In contrast, linkerd is platform-agnostic and can be used with various cloud providers and on-premises environments.

Managed vs. Self-hosted:

AWS App Mesh is a fully managed service, which means that all the operational aspects of the service are managed by AWS.
In contrast, linkerd is a self-hosted service mesh where the user is responsible for the deployment and management of the service mesh.

Integration with Other Tools:

AWS App Mesh integrates seamlessly with other AWS services, such as Amazon Elastic Compute Cloud (EC2), Amazon Elastic Kubernetes Service (EKS), and AWS Fargate.
On the other hand, linkerd can work with any container orchestrator, including Kubernetes.

Traffic Management Capabilities:

AWS App Mesh provides advanced traffic management capabilities, including built-in support for implementing traffic routing and load balancing policies.
In contrast, linkerd offers basic traffic management functionalities but also provides powerful observability features like telemetry and distributed tracing.

Pricing Model:

AWS App Mesh pricing is based on the resources used, such as the number of service meshes, virtual routes, and virtual nodes.
Linkerd, being an open-source service mesh, is free to use without any licensing costs.

AWS App Mesh vs linkerd

Overview

AWS App Mesh vs linkerd: What are the differences?