This guide walks through deploying a demo application on Kubernetes, then demonstrates how to implement canary releases and blue‑green deployments using Nginx Ingress annotations for header‑based, IP‑based, and weight‑based traffic splitting, complete with YAML manifests and verification commands.
This comprehensive guide explains how to design, implement, and operate production‑grade blue‑green and canary releases on Kubernetes, covering traffic control, state handling, capacity planning, observability, automation scripts, code examples, and best‑practice checklists to ensure safe, scalable rollouts in high‑traffic environments.
This comprehensive guide explains HAProxy ACL fundamentals, showcases powerful routing patterns such as multi‑domain, path‑based, header‑based, and canary releases, provides step‑by‑step configuration examples, scripts for runtime adjustments, best‑practice recommendations, troubleshooting tips, and monitoring strategies for production‑grade load balancing.
This guide explains how to achieve a zero‑downtime Kafka cluster migration by deploying a new cluster, configuring MirrorMaker 2 for bidirectional replication, gradually switching producers and consumers, monitoring key metrics, and safely decommissioning the old cluster.
This article explains the blue‑green deployment strategy, introduces Kruise Rollouts’ blue‑green capabilities, provides a step‑by‑step Kubernetes example with YAML manifests and kubectl commands, compares it to Argo Rollouts and Flux Flagger, discusses resource considerations and serverless advantages, and concludes with best‑practice recommendations.
This article outlines six practical strategies to upgrade CI/CD pipelines, including performance and device‑compatibility testing, visual regression and accessibility checks, automated security scans with Dependabot, blue‑green deployments, phased testing, infrastructure‑as‑code integration, and automated rollback checkpoints, helping teams deliver higher‑quality software faster.
Facing MySQL 5.7’s February 2024 end‑of‑life, the team devised a zero‑impact blue‑green migration on AWS RDS to MySQL 8.0.35, using util.checkForServerUpgrade() compatibility checks, pt‑upgrade SQL validation, and a rapid 2‑minute switchover that completed within the planned low‑traffic window.
This article details the background, design principles, overall architecture, concrete refactoring steps, launch process, results, and emerging challenges of implementing a same‑city active‑active solution to improve reliability, load balancing, disaster recovery, and cost efficiency for a large‑scale transaction system.
This guide explains how to implement a blue‑green deployment on Kubernetes with host‑ and path‑based routing, covering prerequisites, namespace creation, deployment manifests, service and ingress configuration, traffic switching, updates, verification, and rollback procedures.
This article explains how Knative leverages request‑driven traffic management to simplify blue‑green releases, configure multi‑gateway ingress, apply revision garbage‑collection policies, enable custom domains, support multiple protocols, and provide automatic scaling and observability through Prometheus and Grafana.
The article examines ZhongAn Bank’s rapid growth in Hong Kong by highlighting its engineer‑first culture, self‑developed core services, agile and blue‑green deployment practices, AI‑driven document recognition, and commitment to inclusive fintech, illustrating how technology fuels its competitive advantage.
This guide explains how to adopt Higress, a high‑performance C++‑based cloud‑native gateway, to replace traditional Java gateways in Spring Cloud ecosystems and demonstrates blue‑green, canary, and A/B testing deployments on Kubernetes using Nacos for service discovery.
The article explains blue‑green deployment as a release strategy that improves large‑scale microservice rollouts by extracting traffic from a blue cluster, incrementally shifting it to a green environment, using global and local traffic scheduling, central metadata, compatible components, and careful considerations such as idempotent consumption and version compatibility.
The article details Meituan’s end‑to‑end design and implementation of Logan, a high‑performance real‑time logging service for mobile apps, web, mini‑programs and IoT, covering background challenges, architecture layers, technology choices such as Flink and Elasticsearch, stability measures, deployment practices, achieved results and future plans.
This article details Ctrip's adoption of Nebula Graph, covering the motivations, distributed architecture, three deployment patterns, Kubernetes‑based operators, client session management, blue‑green read/write splitting, extensive performance tuning, and future roadmap for their production graph database platform.
This article explains how Industrial and Commercial Bank of China (ICBC) adopts gray‑release strategies—including canary, rolling, and blue‑green deployments—combined with standardized specifications, management processes, and automation tools to control version risk, ensure financial stability, and accelerate digital innovation.
Traffic coloring tags each request in a microservice call chain, propagating a version label through HTTP headers or RPC contexts so that routers and load balancers can perform gray releases, blue‑green deployments, lane isolation, graceful shutdowns, and test traffic separation, provided all services support the metadata propagation via frameworks such as Spring Cloud Ribbon or Dubbo.
This article explains the differences between deployment and release, defines continuous deployment, and details various deployment and release strategies such as blue‑green, rolling, dark launch, canary, gray release, and A/B testing, including technical implementations like feature toggles, feature branches, and abstract branches, with real‑world examples from Facebook.
This article provides a comprehensive overview of common microservice patterns and design principles, covering goals such as cost reduction, faster releases, resilience, visibility, and detailing decomposition, integration, database, CQRS, observability, health‑check, and deployment strategies for building robust backend systems.
This guide explains the blue‑green deployment concept, outlines its pros and cons, and provides a step‑by‑step Kubernetes tutorial—including image loading, namespace creation, deployment manifests, service configuration, and traffic switching—to achieve zero‑downtime releases.
This article details a practical smooth‑release process for a cloud‑office system, explains how to use Nginx health‑check endpoints to take instances offline, and presents three AB‑testing routing strategies—IP‑based, cookie‑based, and AB‑cluster proxy—complete with configuration examples, pros and cons, and deployment steps.
This article surveys common software release strategies—stop‑the‑world, canary, gray/rolling, blue‑green, A/B testing, and traffic‑isolation—detailing their advantages, disadvantages, and ideal scenarios, and then presents Alibaba’s practical best‑practice guide for planning, monitoring, and continuously delivering high‑quality releases.
This guide explains what Argo Rollouts is, how to install it, and demonstrates step‑by‑step canary, blue‑green, and traffic‑shifting deployments on Kubernetes using NGINX Ingress, including commands for updating, promoting, aborting, and rolling back releases.
This article explains three key deployment strategies—Blue‑Green, Canary (gray release), and Dark Launch (feature toggles)—detailing their concepts, step‑by‑step traffic switching processes, rollback mechanisms, database considerations, and practical usage scenarios for reliable production releases.
This article explains how the Solar microservice framework, built on Spring Cloud, provides a fully automated, safe, and loss‑less blue‑green release system with intelligent monitoring, weight‑based traffic shifting, and namespace isolation, empowering large‑scale online education platforms to achieve rapid, reliable deployments without manual intervention.
This article explains the principles, advantages, and drawbacks of blue‑green deployment, canary (gray) release, and A/B testing, compares their use cases, and provides step‑by‑step guidance for safely rolling out new versions in modern cloud‑native environments.
This article explains the evolution of Alipay's high‑availability and disaster‑recovery architecture—from a simple single‑datacenter design to a multi‑datacenter, unit‑based system with failover and blue‑green deployment—highlighting the challenges, solutions, and operational benefits that enable continuous service during massive traffic spikes.
This article explains the challenges of validating test cases in production environments, especially for cross‑browser scenarios, and outlines practical strategies—including Selenium Grid automation, blue‑green, canary, and A/B testing—to ensure reliable, efficient production testing.
This article details Youzan's design and implementation of a traffic‑control system built on Istio/Envoy, describing the protocols, architecture, and concrete JSON routing rules for gray releases and blue‑green deployments, along with observability features and future multi‑service release plans.
This article explains the advanced usage of Traefik's IngressRoute, focusing on the cascade feature and how it enables blue‑green deployment and canary release strategies by chaining routes, rewriting paths, and assigning traffic weights across multiple namespaces.
This guide walks through building a Go REST‑API, containerizing it, deploying multiple Knative Service revisions, configuring traffic percentages for gray releases, validating revisions before traffic shift, and rolling back, while comparing Knative’s traffic‑driven model to traditional pod‑based deployments.
ZEIT Now, the serverless platform from the creators of Next.js, provides a fast, parallel, one‑click deployment workflow that automatically builds and deploys front‑end, back‑end, and function code, supports multiple built‑in and custom builders, and enables blue‑green releases and seamless Git integration.
This article explains the risks of using Terraform without proper safeguards, demonstrates a real-world failure caused by careless use of the --auto-approve flag, and presents a robust blue‑green deployment pattern with an arbitration module that enforces safe state transitions on UCloud.
This article explores how dolphins can stay continuously awake by alternating brain hemisphere activity, explains the biological basis of their half‑sleep behavior, and draws analogies to modern software deployment techniques such as blue‑green and rolling updates, illustrating continuous service availability and the concept of perpetual renewal.
This guide explains how to set up Concourse CI pipelines for automated blue‑green deployments, covering Docker Toolbox installation, pipeline configuration, unit and load testing, Cloud Foundry deployment, and cleanup steps, enabling zero‑downtime releases for Node.js applications.
This article examines Alipay's evolution from a simple single‑datacenter setup to a multi‑active‑active, unit‑based architecture, detailing the technical challenges of high availability, disaster recovery, failover design, blue‑green deployment, and how these solutions enable continuous service during massive traffic spikes like Double 11.
This article explains why microservice architectures need reliable communication, load balancing, fault tolerance, monitoring, tracing and circuit breaking, and shows how Istio—a cloud‑native service mesh built on Envoy—provides these capabilities, enabling blue‑green and canary deployments, traffic routing, retries, and observability within Kubernetes.
This article compares four common continuous delivery deployment approaches—minimum‑service deployment, rolling updates, blue/green deployment, and A/B testing—detailing their workflows, advantages, and drawbacks to help teams choose the most suitable method for their applications.
The article explains how Docker’s lightweight container technology speeds up test environment setup, reduces resource consumption, supports blue/green deployments, and simplifies production orchestration, making it an essential tool for modern development teams seeking efficient, reliable software delivery.
