1 views collected around this technical thread.
This article explains how Service Mesh can use traffic coloring to route requests based on headers, cookies, or query parameters, enabling safe canary releases, diversified version testing, and isolated QA environments in complex production systems.
This article provides a concise overview of three common deployment strategies—blue‑green, rolling, and canary (gray) releases—detailing their workflows, advantages, and key considerations for ensuring smooth, low‑risk production updates.
This article introduces and compares three common deployment strategies—blue‑green, rolling, and canary (gray) releases—detailing their workflows, advantages, drawbacks, and practical considerations for safely delivering new software versions.
This article explores essential microservice traffic management techniques—including canary releases, A/B testing, and traffic shading—detailing their value, implementation steps, and practical examples using Service Mesh and Istio, with code snippets and diagrams to illustrate routing based on request attributes.
This comprehensive guide clarifies the differences between deployment and release, explores continuous deployment concepts, details various deployment and release strategies such as blue‑green, rolling, dark launch, canary, gray, and A/B testing, and examines supporting technologies like feature toggles and branch‑by‑abstraction, illustrated with a Facebook case study.
This article describes Ctrip's cloud‑native Service Mesh deployment, detailing its multi‑IDC high‑availability design, fault‑scenario analysis, xDS push metrics, event‑handling optimizations, cold‑start improvements, and progressive canary release strategies to ensure reliable, scalable service traffic management.
This article explains the concept of canary (gray) releases, demonstrates how to perform rolling updates and precise traffic splitting in Kubernetes, and shows how to achieve fine‑grained canary deployments using Istio’s VirtualService and DestinationRule resources with practical YAML and kubectl examples.
This article explains the concept of progressive delivery, its industrial origins, how cloud‑native tools like Kubernetes, Traefik and Spinnaker enable automated A/B testing, canary and gray releases, and the practical benefits for developers, operations, and product teams when releasing features to millions of users.
This comprehensive guide explains the differences between deployment and release, defines continuous deployment and on‑demand release, and details practical strategies such as blue‑green, rolling, dark launch, canary, gray, and A/B testing, supported by feature toggles, feature branches, and real‑world Facebook case studies.
The article explains the challenges of API version control, introduces canary release as an alternative deployment strategy, and illustrates its practical implementation at ING Bank, highlighting benefits such as gradual rollout, easy rollback, and improved stability for continuously evolving APIs.
This article details the design and evolution of Zhihu's deployment platform, covering its early physical‑machine system, the transition to container orchestration with Mesos and Kubernetes, and advanced features such as blue‑green, canary releases, pre‑deployment, and branch deployments that enable rapid, reliable continuous delivery for large‑scale internet services.
The article recounts Visual Studio Online’s 2013 launch outage, explains how Microsoft adopted multi‑region scaling, canary releases, continuous integration, and feature‑flag patterns to transition from Agile to DevOps, and shows how these practices dramatically improved service stability and accelerated product delivery.
This article reviews common deployment strategies—Blue/Green, Rolling Update, and Canary/Gray releases—explaining their definitions, characteristics, step‑by‑step processes, advantages, drawbacks, and practical considerations for minimizing risk during software rollouts.