Docs

Volcengine Kubernetes Engine

Solution

Cloud-based architecture solution for large-scale concurrent business systems

This topic describes a cloud architecture solution for large-scale concurrent business systems built on VKE.

Solution introduction

Business systems that serve large user bases generally need to be deployed in large-scale concurrent architectures to handle rapidly increasing business access. This effectively ensures business availability, reduces system overhead, improves business efficiency, and saves costs.

Typical business scenarios include:

E-commerce web systems

Fast-growing mobile apps

In these scenarios, traffic can surge during specific periods, so the architecture must support temporary business expansion without requiring a full system redesign or optimization.

We recommend that you use the following cloud-based architecture for large-scale concurrent business systems based on the preceding requirements:

Use CDN to forward static content to effectively reduce load on public network egresses and enhance system robustness.

Use Classic Load Balancer (CLB) to distribute access requests, reduce traffic hotspots on individual points, and improve overall system resource utilization. Use CLB together with the autoscaling capabilities of VKE to achieve quick scale-out to process continuously increased business access requests.

Use VKE to deploy core application modules so that they can be built and upgraded quickly. Combined with CP and other pipeline capabilities, VKE also helps establish DevOps practices and improve delivery efficiency.

Use CR to effectively support image storage and distribution needs.

Use Redis to accelerate access to hot data and enhance system access support.

Use cloud databases to provide multi-replica, high-performance, and highly reliable database services.

Use TOS for static data storage at low costs.

Use services, such as APMPlus, VMP, IAM, Cloud Monitor, and TLS, to build a cloud-based operation and maintenance management platform that meets system operation and maintenance requirements.

Solution advantages

Massive cloud resources meet quickly increasing access requirements for businesses.

High availability design for cloud services effectively enhances system stability and availability.

Specialized operation and maintenance services and back-end support teams reduce the technical difficulty and complexity of operation and maintenance management.

Comprehensive security infrastructure and management systems ensure business and data security.

Prerequisites

Complete real-name authentication for the account. For instructions, see Real name authentication.

ICP filing has been completed for the access domain name in Volcano Engine. For instructions, see ICP filing process.

Deploy the application in containers. For instructions, see Deploying applications.

Upload the image to CR. For instructions, see Pushing and pulling images.

(Optional) Set up a Redis database. For Redis instructions, see Cache for Redis usage process.

(Optional) TOS has been integrated. For instructions, see Getting started with TOS.

Docker has been installed. For specific operations, see Installing Docker.

Procedure

Step 1: Upload business container images to CR

tip

For detailed operating instructions, see Getting started with CR.

Configure a password to access the repository. This password is required for docker login when using CR.

Create a namespace.

Create an OCI artifact repository.

Push and pull images.

Run the following command to log in to the CR instance.

docker login --username=<volcengine_username>@<UserID> cr-cn-<image_repo_instance_region>.volces.com
##Example:
##docker login --username=v**@100**** cr-cn-beijing.volces.com

Run the following command to tag a local image.

docker tag [ImageId or image_name] cr-cn-<image_repo_instance_region>.volces.com/<namespace_name>/<image_name>:[image_tag]
##Example
##docker tag mysql cr-cn-beijing.volces.com/space/mysql:latest

Run the following command to push the image to the CR instance.

docker push cr-cn-<image_repo_instance_region>.volces.com/<namespace_name>/<image_name>:[image_tag]
##Example
##docker push cr-cn-beijing.volces.com/space/mysql:latest

After the image is transferred, you can query the specified container image in the CR instance and use this image to create an application workload in VKE.

Step 2: Upload static content to TOS

tip

For detailed operating instructions, see Getting started with TOS.

Activate the TOS service. Log in to the TOS console and activate the TOS service based on the on-screen prompts.

Create a bucket. For details, see Creating buckets.

Upload files. For detailed operations, see Uploading files.

Step 3: Create a database

Create a database based on your business requirements, such as MySQL or Redis.

tip

You can create a Redis database in the same way as creating a MySQL database described in the following content. For detailed operating instructions, see Getting started with databases or Getting started with cache databases.

Create an instance: Create an RDS for MySQL instance and confirm the instance version and instance specification. For the method of creating an instance, see Creating instances.

Create a database and account: Create a database and account based on your business requirements, and configure account permissions. For details, see Creating databases and accounts.

Configure an IP allowlist: Only devices added to the allowlist can access the instance. For details, see Adding IP addresses to allowlists.

Connect to the instance: You can use multiple methods such as a client or the command line to connect. For specific methods, see Connecting to databases.

Step 4: Create a CLB instance and associate an EIP

tip

For detailed operating instructions, see Getting started with CLB.

Create a CLB instance: Create a CLB instance based on your business scenarios and traffic volume.

Create a back-end server group: Create a back-end server group and add back-end servers to provide services.

Create a back-end server group.

Add back-end servers.

Create a listener: Add a listener to the instance and associate it with the back-end server group.

Step 5: Create a VKE cluster and deploy business-related workloads

tip

For detailed operating instructions, see Getting started with VKE and VKE user guide.

Create a cluster. For detailed steps, see Creating clusters.

Deploy an application. For detailed operating instructions, see Creating Deployments.

Access the application.

On the Deployment page, click the name of the created Deployment.

On the Deployment details page, click the Access method tab.

On the Access method tab, click the Service tab, and then click Create Service.

On the Create Service page, configure service information. After you complete the configuration, click Confirm in the lower-right corner of the page.

On the Deployment details page, click the Access method tab. Copy the address in the External endpoint column on the Service tab.

In the browser address bar, enter the External endpoint address. If the application can be accessed as expected, it indicates that the application is deployed.

Monitor the application.

After the application is deployed, you can use the Cloud Monitor service to monitor the status of the application, including CPU and memory usage, to provide support for operation and maintenance. For details about observability in VKE, see Enabling observability.

Step 6: Develop business logic

Develop the business logic in the database based on your business system plan.

Step 7: (Optional) Connect to CDN

tip

For detailed operating instructions, see Getting started with CDN.

Activate the CDN service. For detailed operating instructions, see Activating the service.

Create an accelerated domain name. For detailed operating instructions, see Creating accelerated domain names.

Configure a cache rule. For detailed operating instructions, see Configuring cache rules.

Configure traffic routing. The configuration interface varies based on different domain service providers. For the configuration methods in mainstream DNS resolution service providers, see Configuring traffic routing.

Operation result

After you perform the preceding operations, you can build a system based on VKE for large-scale concurrent business scenarios.

Last updated: 2026.07.23 11:53:58