0 views collected around this technical thread.
This article explains three common software release strategies—blue‑green deployment, rolling deployment, and canary (gray) deployment—detailing their principles, advantages, potential pitfalls, and practical considerations, while also contrasting them with A/B testing and noting related operational concerns.
This article introduces common release strategies—blue‑green deployment, rolling updates, and canary (gray) releases—detailing their workflows, advantages, drawbacks, and practical considerations, and clarifies how they differ from A/B testing in modern software delivery.
The article introduces common release techniques—blue‑green, rolling, and canary (gray) deployments—explaining their principles, advantages, drawbacks, and practical considerations, and distinguishes them from A/B testing in modern software delivery pipelines.
The article explains how separating code deployment from feature release reduces risk by describing deployment versus release concepts, low‑risk release goals, and detailed techniques such as environment‑based (blue‑green, canary, rolling) and application‑based (feature toggles, A/B testing, dark launch) strategies within DevOps.
This article explains how microservice architectures require a comprehensive testing strategy that combines traditional pre‑production tests—unit, integration, component, contract, and end‑to‑end—with production‑focused techniques such as fault injection, canary, blue‑green, and multivariate testing to ensure reliable continuous delivery.
The article explains common release strategies—including blue‑green deployment, rolling updates, canary (gray) releases, and A/B testing—detailing their principles, advantages, limitations, and practical considerations for safely delivering new versions in production environments.
This guide explains the principles, installation via Helm, example deployments, authentication, URL rewriting, canary releases, TLS setup, TCP/UDP service exposure, and global configuration of the nginx-based ingress-nginx controller for Kubernetes clusters.
This article introduces three common release strategies—blue‑green deployment, rolling deployment, and canary (gray) deployment—explaining their workflows, advantages, drawbacks, and practical considerations for safely updating production systems during iterative project releases.
This article reviews the main deployment techniques—blue‑green, rolling, canary (gray) releases and A/B testing—explaining their principles, advantages, drawbacks, and practical considerations for safely delivering new versions during iterative project development.
This article explains common deployment strategies—including blue‑green, rolling, canary (gray) releases, and A/B testing—detailing their principles, advantages, drawbacks, and practical considerations for safely delivering new versions in production environments.
The article explains four major software release strategies—blue‑green deployment, rolling release, canary (gray) release, and A/B testing—detailing their principles, advantages, drawbacks, and practical considerations for safely rolling out new versions in production environments.
This article details the evolution of Zhihu's deployment platform, covering its early physical‑machine system, the transition to container orchestration with Kubernetes, and the implementation of blue‑green, canary, and pre‑release strategies that enable fast, reliable continuous deployment.
This article explains how Kubernetes uses Deployments, ReplicaSets and Pods to manage containerized applications, covering basic object creation, scaling, rolling updates, readiness probes, rollback, maxSurge/maxUnavailable settings, and advanced strategies such as blue‑green and canary deployments.