Tagged articles
deployment strategy
12 articles · Page 1 of 1
Tencent's Hy4 official release adds vision understanding and computer operation while keeping preview pricing (6/18/0.3 yuan per million tokens), but weights remain closed; the article benchmarks capabilities, highlights evaluation caveats, calculates real-world costs, and gives adoption guidance for cloud, private, local, and cost-sensitive teams.
Hy4LLMOpen Source
0 likes · 10 min read

This article details a practical blue-green deployment workflow using Nginx and Docker on a single Linux server, covering health checks, version verification, candidate validation, atomic Nginx upstream switching, rollback procedures, database compatibility, static asset versioning, and graceful shutdown of old instances.
blue-green-deploymentdeployment strategydocker
0 likes · 34 min read

This article explains why canary releases become essential at 10M QPS, detailing how to define canary units by identity, failure domain, and business scenario; set absolute traffic limits; use evidence-driven state machines with four metric layers; ensure version compatibility; choose rollback, feature-flag, or forward-fix strategies; build platform capabilities; avoid common pitfalls; and make canary the default deployment path.
10M QPSRollback StrategyVersion Compatibility
0 likes · 30 min read

This guide explains the core principles and four essential techniques—accurate probes, proper deployment strategies, lifecycle hooks, and advanced modes like blue‑green or canary—to reliably perform zero‑downtime releases on Kubernetes clusters.
KubernetesLifecycle HookReadiness Probe
0 likes · 7 min read

This article explains the concept of gray (canary) release, why it’s essential for large‑scale architectures, outlines the step‑by‑step workflow, describes common traffic‑splitting strategies, and offers practical tips for monitoring and gradually scaling deployments to ensure system stability.
Gray Releasecanary deploymentdeployment strategy
0 likes · 4 min read

The rolling deployment strategy incrementally replaces old application instances with new ones, allowing users to encounter both versions during rollout, and is praised for ease of implementation, low risk, and default support in platforms like Kubernetes, though it can be slow, costly for large infrastructures, and may affect user experience.
Kubernetesdeployment strategyoperations
0 likes · 2 min read

This article explains the concept of gray release, outlines a simple architecture with essential components, describes common traffic-splitting strategies, shows how to implement control in Nginx and service layers, and discusses complex scenarios such as multi‑service and data‑centric deployments.
A/B testingBackend ArchitectureGray Release
0 likes · 7 min read

This article explains gray release (canary deployment) as an A/B testing‑style rollout, outlines a simple architecture with strategy configuration, execution, and service registry components, describes common traffic‑splitting strategies, and discusses implementation details for Nginx, gateway layers, and complex multi‑service and data‑centric scenarios.
A/B testingGray Releasecanary deployment
0 likes · 6 min read

This article explains the concept of gray release, outlines a simple architecture with essential components, describes common routing strategies, and shows how to implement gray releases using Nginx, gateway services, and complex multi‑service scenarios to ensure controlled, low‑risk deployments.
A/B testingGray Releasedeployment strategy
0 likes · 7 min read

This comprehensive technical guide explores practical Flutter cross-platform development strategies, detailing architectural design, hybrid engineering integration, routing management, MVVM state handling, platform adaptation, and robust deployment practices including grayscale release, real-time monitoring, and automated rollback mechanisms for mobile applications.
Cross-platform DevelopmentFlutterHybrid Engineering
0 likes · 15 min read

The article explains gray release as a smooth, risk‑mitigating deployment method, outlines why it is needed, describes its limitations, and compares four practical gray‑release solutions—including code‑level flags, pre‑release machines, SET isolation, and dynamic routing—before recommending a combined approach.
Gray Releasecanary deploymentdeployment strategy
0 likes · 11 min read

This article describes the reconstruction of an order‑reservation‑refund system, detailing business background, abstraction of reservation flows, layered business classification, validation stack implementation, unified data models, mechanism‑strategy separation, and step‑by‑step deployment practices for a robust backend service.
Backend RefactoringDesign Patternsdeployment strategy
0 likes · 13 min read
