An Overview of the USP Deployment System: Architecture, Models, and Key Features

Deployment is a crucial step in software development and continuous delivery; this article introduces the 58 Deployment System (USP), describing its evolution, architecture, communication model, deployment model, traffic management, one‑stop deployment, parallel deployment, gray‑scale deployment, fast rollback, and task‑driven workflow.

System Architecture

USP is a Java‑based web application; its architecture follows a typical Java web project layout.

Communication Model

USP uses a ZooKeeper‑based agent component installed on target servers; the agents communicate with the USP backend, which distributes deployment commands to agents for execution.

Deployment Model

USP defines a standardized deployment process that abstracts each step into modules, allowing both common and custom deployment flows for different business types.

For generic business types, USP provides preset deployment steps; for non‑generic types, users can configure custom steps.

Traffic Management

During deployment, USP interacts with the front‑end Nginx proxy to switch traffic, ensuring the target servers are isolated, and offers weight‑adjustment features for fine‑grained traffic distribution.

One‑Stop Deployment

USP supports automated deployment across testing, sandbox, production, and stable environments, covering the full lifecycle from development to release.

Parallel Deployment

USP calculates an appropriate concurrency range based on the number of server instances, allowing users to set the desired parallelism for multi‑server deployments.

Users configure the concurrency degree via a form, and USP executes deployments concurrently across selected servers.

Gray‑Scale Deployment

USP enforces gray‑scale deployment for clusters with at least two instances, requiring a partial rollout before full production release.

Fast Rollback

USP backs up each deployed version; users can create a rollback task to revert to a previous version quickly.

Task‑Driven Workflow

Each deployment generates a closed‑loop task that records operations, steps, and status, giving fine‑grained control and traceability.

Conclusion

With the adoption of private‑cloud and container technologies, USP currently supports deployments on physical and virtual machines and will evolve toward lightweight, customizable services.