How Bosideng Achieved Seamless Cloud‑Native Transformation with Kubernetes and MSE

Background

Bosideng, founded in 1976, is a global leader in down‑coat research, design and manufacturing, with 26 years of sales leadership and products sold in over 72 countries.

Digital and Cloud‑Native Transformation

To support its digital business, Bosideng completed a full‑stack digital transformation covering production, warehousing, logistics and sales. It built a data‑center platform to unify channel data and empower consumer research, product planning and channel matching. Each down‑coat now follows a “digital journey” from factory to consumer.

Cloud‑Native Technology Development

Bosideng follows two principles: fully embrace open‑source standards and leverage cloud computing for non‑functional requirements. Kubernetes, as a de‑facto open‑source standard, is used together with Alibaba Cloud Container Service (ACK) to simplify operations and integrate cloud resources.

Containerization Refactoring

Since 2021 Bosideng migrated its services from virtual machines to Kubernetes. ACK provides the Terway network mode that places containers and VMs on the same network layer, enabling gradual containerization without service interruption. The migration raised resource utilization by 30 % and operation efficiency by 40 %.

Unified Microservice Architecture

Previously, each business unit used different tech stacks, causing high coupling and slow delivery. Under CIO Dai Jianguo, Bosideng standardized on Spring Cloud Alibaba for Java‑based microservices, achieving a unified framework and dramatically improving development speed.

Microservice Challenges

Two main issues emerged: difficulty locating performance problems due to long call chains, solved with Alibaba Cloud ARMS and Prometheus/Grafana; and frequent application changes causing incidents, addressed by establishing safe‑change processes and governance.

Downline Loss Problem

When a service instance goes offline, a time gap between deregistration and consumer cache refresh can cause request failures. Bosideng attempted a /offline endpoint and pre‑stop scripts, but residual failures remained.

Upline Loss Problem

During scaling‑up, new instances experience a 3‑5 minute performance bottleneck due to uninitialized async resources (DB/Redis connections, class loading, JIT compilation). Pre‑warm traffic and parallel class loading are used to mitigate this.

Safe Change and Gray‑Release

Bosideng adopted gray‑release principles (canary, monitoring, rollback). Initially it used physical isolation (duplicate environments) but moved to logical isolation, routing traffic based on gray tags, reducing resource waste and coordination overhead.

MSE Microservice Governance

After evaluation, Bosideng adopted Alibaba Cloud MSE, which offers non‑intrusive Java Agent‑based governance, simple integration, high stability, observability, hybrid‑cloud support and seamless Kubernetes integration. MSE enables lossless up/down scaling, traffic control, and full‑link observability.

Lossless Down/Up Scaling

MSE’s Agent automatically deregisters the instance, notifies all consumers, and updates load‑balancer lists, ensuring no request is lost during downscale. For upscale, MSE pre‑heats new instances and gradually shifts traffic, avoiding JIT‑related spikes.

Full‑Link Traffic Governance

Using MSE, Bosideng implements canary releases with traffic coloring and version tagging, achieving logical isolation and gradual rollout. The system also provides adaptive rate‑limiting, fault detection, and database governance to protect against slow SQL and overload.

Results

With MSE, Bosideng’s business iteration speed doubled, production incidents dropped by over 70 %, and the company sustained double‑digit revenue growth while supporting million‑level concurrent traffic during major sales events.