Envoy Proxy in 2019: Security, Caching, Wasm, HTTP/3, and more

Envoy Proxy in 2019: Security, Caching, Wasm, HTTP/3, and more

  • August 3, 2019
Table of Contents

Envoy Proxy in 2019: Security, Caching, Wasm, HTTP/3, and more

Since its release in September 2016, Envoy Proxy has gained enormous traction in the market. Envoy was a classic case of the right product at the right time: Envoy had the right set of features and performance to address this need. Some of these features included a runtime API for configuration & management, dynamic configuration, gRPC & HTTP/2 support, automatic retries, traffic shadowing, and robust observability systems.

These factors created critical mass, driving rapid adoption. Envoy also quickly found a neutral home in the Cloud Native Computing Foundation, and, led by Lyft, quickly grew a vibrant developer community, with organizations such as AirBnb, Google, Lyft, Pinterest, Verizon, and others contributing. Envoy’s success has not gone unnoticed by the competition.

A year after Envoy’s announcement, HAProxy added a runtime API, hitless reloads, and HTTP/2 support in HAProxy 1.8, and, in June 2019, shipped HAProxy 2.0 with support for L7 retries, traffic shadowing, and gRPC.11 months after Envoy’s announcement, NGINX added a runtime API and shadowing in NGINX Plus R13, and in March 2018, added native support for gRPC in open source NGINX.

Source: getambassador.io

Tags :
Share :
comments powered by Disqus

Related Posts

How to Write Envoy Filters Like a Ninja!—Part 1

How to Write Envoy Filters Like a Ninja!—Part 1

Envoy is a programmable L3/L4 and L7 proxy that powers today’s service mesh solutions including Istio, AWS App Mesh, Consul Connect, etc. At Envoy’s core lie several filters that provide a rich set of features for observing, securing, and routing network traffic to microservices. In these set of posts, we’ll have a look at the basics of Envoy filters and learn how to extend Envoy by implementing custom filters to create useful features!

Read More
Envoy Proxy at Reddit

Envoy Proxy at Reddit

Reddit’s engineering team and product complexity has seen significant growth over the last three years. Facilitating that growth has taken a lot of behind-the-scenes evolution of Reddit’s backend infrastructure. One major component has been adopting a service-oriented architecture, and a significant facet of that has been evolving service-to-service discovery and communication.

Read More
A Crash Course For Running Istio

A Crash Course For Running Istio

At Namely we’ve been running with Istio for a year now. Yes, that’s pretty much when it first came out. We had a major performance regression with a Kubernetes cluster, we wanted distributed tracing, and used Istio to bootstrap Jaeger to investigate.

Read More