How a Used‑Car Business Achieved 100% Containerization in One Month

In October the used‑car business unit began deploying its applications to containers. Within a month the containerization rate jumped from 3.33% to 100%, making the division the first in the company to achieve full‑traffic, full‑application containerization and supporting 120 million daily calls.

Interview Overview

The cloud‑operations team interviewed the division’s technical director, Ji Wang, and the designated container liaison, Xu Yaqiang, to capture their motivations, methods, and reflections.

Motivation for Container Adoption

Ji Wang explained two main drivers: (1) cost reduction – containers consume far less resources than virtual machines; (2) strategic alignment – containerization follows industry trends and positions the team for future technology directions.

Rapid Deployment Strategy

To meet a one‑month deadline, the team set a clear, non‑negotiable goal, assigned two senior engineers (Xu Yaqiang and Han Hua) to receive intensive container‑training, pilot the process, and then mentor the rest of the team, minimizing disruption to regular development work.

Technical Challenges and Solutions

Identifying individual container instances: because containers lack static host identifiers, the team logged each container’s IP address to uniquely tag log entries.

Environment inconsistencies: differences between classic VM deployments and containers caused start‑up failures; systematic log analysis helped pinpoint and resolve these issues.

.NET Core 3.0.100 database connectivity: the containerized app repeatedly failed to connect to the database. After testing with other languages and confirming the network path, the team discovered an SSL version bug in the official image’s Git repository, fixed it by adjusting the Dockerfile, and restored database connectivity.

Impact on Individual Developers

Xu Yaqiang noted that, compared with traditional deployments, containerization dramatically shortened deployment time, freeing him to focus more on coding rather than lengthy environment setup.

Team‑Level Benefits

Ji Wang highlighted several improvements: immutable infrastructure defined by Dockerfiles, consistent environments across testing and production, on‑demand resource scaling via a shared container pool, and reduced communication overhead, all of which elevated the team’s operational efficiency.

Future Expectations

The team hopes to lower the learning curve by packaging common configurations into visual, reusable templates, enhance shared services such as up‑to‑date base images and centralized logging, and further explore advanced container features like automatic scaling and service‑mesh architectures.

Upcoming plans include a similar full‑scale containerization effort by the e‑commerce technology team, with lessons from both business units to be shared later.