Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Envoy Content on InfoQ


RSS Feed
  • eBPF and the Service Mesh: Don't Dismiss the Sidecar Yet

    While eBPF looks promising to improve service mesh sidecar proxy performance, there are other, simplier ways to improve performance. The layer 7 processing needed for service meshes is unlikely to be feasible in eBPF for the foreseeable future, which means that meshes will still need proxies.

  • The What and Why of Programmable Proxies

    A question which gets often asked is “What is a programmable proxy, and why do I need one?” This article tries to answer this question from different perspectives. We will start with a brief definition of what a proxy is, then discuss how proxies evolved, explaining what needs they responded to and what benefits they offered at each stage. Finally, we discuss several aspects of programmability.

  • Data Patterns for the Edge: Data Localization, Privacy Laws, and Performance

    With growing competition to get data that power experiences to the end-user closer and closer and the advent of local data privacy laws, let's look at different enterprise data patterns like “synchronous data retrieval”, “subsequent data retrieval” and “prefetch data retrieval” on data center.

  • The Potential for Using a Service Mesh for Event-Driven Messaging

    In this article, we discuss one of the most challenging and unexplored areas in service mesh architecture; supporting event-driven messaging. There are two main architectural patterns that we discuss here: the protocol proxy sidecar, and the HTTP bridge sidecar. Regardless of the pattern that is used, the sidecar can facilitate features such as observability, throttling, tracing etc.

  • API Gateways and Service Meshes: Opening the Door to Application Modernisation

    Modernising applications by decoupling them from the underlying infrastructure on which they are running can enable innovation, reduce costs, and improve security. An API Gateway can decouple applications from external consumers, and a service mesh decouples applications from internal consumers.

  • Ambassador: Building a Control Plane for an Envoy-Powered API Gateway on Kubernetes

    This article provides an insight into the creation of the Ambassador open source API gateway for Kubernetes, and discusses the technical challenges and lessons learned from building a developer-focused control plane for managing ingress or "edge" traffic within microservice-based applications.

  • Envoy Service Mesh Case Study: Mitigating Cascading Failure at Lyft

    Over the past four years, Lyft has transitioned from a monolithic architecture to hundreds of microservices. As the number of microservices grew, so did the number of outages due to cascading failure or accidental internal denial of service. Today, these failure scenarios are largely a solved problem within the Lyft infrastructure due to the use of the Envoy Proxy as a service mesh.