InfoQ Homepage Service Mesh Content on InfoQ
-
DoorDash Uses Service Mesh and Cell-Based Architecture to Significantly Reduce Data Transfer Costs
In a recent move, DoorDash has significantly optimized its cloud infrastructure costs. The company faced increased cross-AZ data transfer costs when transitioning to a microservices architecture. To substantially reduce this cost, DoorDash implemented zone-aware routing with its Envoy-based service mesh, taking advantage of its Cell-Based Architecture.
-
Slack Migrates to Cell-Based Architecture on AWS to Mitigate Gray Failures
Slack migrated most of the critical user-facing services from a monolithic to a cell-based architecture over the last 1.5 years. The move was triggered by the impact of networking outages affecting a single availability zone, causing user-impacting service degradation. The new architecture allows incrementally draining all the traffic away from the affected availability zone within 5 minutes.
-
Reddit Unveils REV2: Modernised Rule-Execution with Kubernetes, Kafka, and Flink Stateful Functions
Reddit's Safety Engineering team recently published how it modernised its Rule-Execution system, which detects and acts on policy-violating content in real time. The new architecture includes improvements like transitioning from legacy EC2-based systems to Kubernetes, better rule version control with Github and S3 storage, and the capability to scale more efficiently with Flink Stateful Functions.
-
Linkerd 2.14 Improves Support on Flat Networks and Gateway API Conformance
Version 2.14 of Linkerd, a service mesh and graduated CNCF project, has been released, with improved enterprise multi-cluster support, full Kubernetes Gateway API conformance, and many other changes.
-
Implementation of Zero-Configuration Service Mesh at Netflix
In a recent blog post, Netflix described why they engaged the Envoy community and Kinvolk to implement a new feature for Envoy, the open-source proxy developed by Lyft. This new feature called On-Demand Cluster Discovery helped Netflix to implement a zero-configuration service mesh.
-
Consul 1.16 Released with Reliability, UX and Security Improvements
Consul 1.16 - the latest version of Hashicorp's service mesh tool - has been released. This release contains many enhancements that improve service mesh reliability, user experience, and security.
-
Real-Time Messaging Architecture at Slack
Slack recently described how it sends millions of messages daily in real-time across the globe. The company provides a comprehensive insight into its architecture, designed to manage real-time messages at scale. It highlights the unique challenges posed by delivering real-time messages across different time zones and regions and how Slack's engineers designed the infrastructure to handle them.
-
HashiCorp Consul Improves Envoy Integration, Adds Debugging Tool
HashiCorp has released Consul 1.15, adding new features that improve interacting with Envoy and troubleshooting issues within the service mesh platform. The release introduces improvements to Envoy access logging as well as adding in Consul Envoy extensions. To improve the troubleshooting experience, a new service-to-service troubleshooting tool has been added.
-
Service Mesh Kuma Improves Policy Handling and Debugging Experience
Kuma, a service mesh technology, released version 2.1 with improved policies and an updated UI. The improved policies build upon the 2.0 release and move the remaining policies over to the new targetRef system. The targetRef system provides an improved matching system for defining policies.
-
HashiCorp Consul Introduces New Sidecar Model for Kubernetes Deployments
HashiCorp has released Consul 1.14, adding new features that simplify deployments and improve the resiliency of their service mesh platform. The release includes Consul Dataplane, an improved architecture for deploying onto Kubernetes. The cluster peering model that was introduced as beta in 1.13 has been moved into full general availability.
-
CNCF Accepts Istio as an Incubating Project
The CNCF recently announced that it has voted to accept Istio as an incubating project. Initially developed by Google and IBM alongside the Lyft team, Istio is the most widely adopted service mesh. The Istio steering committee shared the announcement in a blog post, reflecting on Istio’s journey from 2016.
-
Atlassian Exceeds 99.9999% of Availability Using Sidecars and Highly Fault-Tolerant Design
Atlassian recently published how it exceeded 99.9999% of availability with its Tenant Context Service. Atlassian achieved this high availability by implementing highly-autonomous client sidecars, able to proactively shield themselves from complete AWS region failures. Sidecars query multiple services concurrently to accomplish this goal and ensure that requests are entirely isolated internally.
-
HashiCorp Consul on Amazon ECS Adds Development Kit and Support for High Traffic Loads
HashiCorp has announced the release of version 0.3 of their Consul on Amazon ECS service. The release includes support for additional configuration options, deployment without Terraform, and confirmed support for high traffic loads. They have also released, in partnership with AWS, a AWS Cloud Development Kit (CDK) to support using Consul on Amazon ECS.
-
HashiCorp Consul API Gateway Adds TCPRoute Support and Installation via Helm Chart
HashiCorp has moved their Consul API Gateway into beta release. The release adds a number of new features to their Consul Service Mesh ingress solution including support for TCPRoute, installation via Helm Chart, and TLS settings per listener.
-
Solo.io Open Sources BumbleBee to Make eBPF Development Easier
Solo.io recently announced an open-source project called BumbleBee, which aims to simplify eBPF application development through auto-generated templates and boilerplate files.