This article describes how to implement traffic lanes in permissive mode for bidirectional communication applications built with WebSocket.
This article introduces a multi-environment deployment and end-to-end canary release solution under multi-cluster deployment proposed by ASM.
This article provides an overview of canary release practices from a DevOps perspective, explaining how to integrate canary release with DevOps workflows.
This article introduces three common types of master-worker architectures and discusses the challenges of preventing cascading failures in distributed systems.
This article discusses the concept and practice of end-to-end canary releases, particularly in the context of microservices.
MSE provides a set of mature functions in the end-to-end canary release scenario of microservices and supports canary routing policies of content rules and percentage rules.
This article describes how to use OpenKruise to build automated O&M.
This article introduces by Kruise Rollout’s solution for enhancing traffic scheduling capabilities for progressive delivery.
Part 4 of this 4-part series describes how to use traffic labels to implement an end-to-end canary release for microservices.
This article describes how to use Container Service for Kubernetes (ACK) and MSE Ingresses to manage ingress traffic in clusters.
This article introduces full-process grayscale capability and explains common solutions for full-process grayscale capability on databases with specific examples.
Part 2 of this 3-part series discusses ArgoCD, Sidecar mode, and automatic rollback with Prometheus.
This article defines progressive delivery and explains the purpose of Kruise Rollout.
Part 22 of this 27-part series describes multiple release strategies, including advantages, disadvantages, and applicable scenarios.
This article explains how MSE microservice governance works with Laidian Technology to continuously improve the R&D efficiency of microservices.