Application Scenarios
  • Gaming

  • E-Commerce

  • Internet

  • Finance

  • Enterprise

Gaming

Gaming

The Redis sorted set data structure simplifies leaderboard creation and enables fast access to leaderboards.

Advantages

Fast Data Access

Retrieve frequently used data (such as leaderboards) from an in-memory data cache instead of relying entirely on slower disk-based databases.

Scalability

With just a few clicks, resize your DCS instances online to accommodate application load spikes.

Backup and Restoration

Back up data to OBS and restore it with just a few clicks.

Related Services

ecs

elb

obs

E-Commerce

E-Commerce

DCS for Redis provides fast concurrent access to frequently requested data, such as best sellers and daily deals, and is scaled easily as load increases.

Advantages

High Concurrency

DCS for Redis supports up to 100,000 queries per second.

Easy Scalability

With just a few clicks, your DCS instances can be resized online to accommodate application load spikes.

Data Persistence

Data is automatically persisted to disk, maintaining data durability and security.

Related Services

ecs

elb

mysql

Internet

Internet

DCS for Redis is ideal for social networking and web apps. The Redis Set data structure can maintain friend connection data, while the Redis String data structure can maintain static cache files.

Advantages

High Concurrency

DCS for Redis supports up to 100,000 queries per second.

Pay-per-Use

Get the DCS instances you need and only pay for what you actually use.

Easy Scalability

With just a few clicks, your DCS instances can be resized online to accommodate application load spikes.

Related Services

ecs

elb

mysql

Finance

Finance

DCS for Redis delivers high concurrency, security, and data reliability for financial apps.

Advantages

High Availability

HA architecture ensures that faults in a single cache node do not affect services.

Security

Security measures include requiring credentials (username and password) and providing audit logs.

Backup and Restoration

Data can be backed up to OBS and restored with just a few clicks.

Enterprise

Enterprise

Traditional enterprise apps require a large amount of code with complex data processing logic. Existing relational databases are slow, requiring local optimization to accelerate response.

Advantages

SQL Statements

Supports standard SQL statements such as DML and DDL.

ACID Transactions

Supports concurrent success/failure, simplifying the processing logic at the application layer.

JCache API

Supports integration with external databases.

Related Services

obs

vpn

Functions

  • Multiple Cache Engines

    You can choose between two cache engines, Redis and IMDG, depending on your requirements.

  • High Availability

    If a master cache node becomes faulty, the standby cache node will take over within seconds.

Multiple Cache Engines

  • Redis

    Redis is an in-memory data structure store. It supports data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs and geospatial indexes with radius queries. There are three types of DCS Redis instances: single-node, master/standby, and cluster.

  • IMDG

    An IMDG is an in-memory data structure. It improves data access by using the memory computing capabilities of each node after clustering.

High Availability

  • Cluster DCS Instances

    Each shard of a cluster DCS instance is held on both the master and standby cache nodes. If the master node fails, the standby node takes over, without affecting applications.

  • Master/Standby DCS Instances

    Applications will not perceive any failover because the IP address exposed to them remains unchanged when the standby node takes over in the event of a master node failure.

  • Flexible Specs

    You can choose among single-node, master/standby, and cluster instances from 2 GB to 1024 GB.

  • Scalability

    DCS instances can scale online and hitlessly as the instance load increases.

Flexible Specs

  • Single-Node DCS Instances

    Each DCS instance runs on only one cache node and provides storage capacity of 2 GB to 64 GB. This type of DCS instance is recommended when only caching is needed.

  • Cluster DCS Instances

    Each DCS instance provides storage capacity of 64 GB to 1024 GB, and runs in cluster mode. This type of DCS instance is recommended when high scalability and concurrency are needed.

  • Master/Standby DCS Instances

    Each DCS instance provides storage capacity of 2 GB to 64 GB and runs on two cache nodes, one master and one standby. This type of DCS instance is recommended when high availability is needed.

Scalability

  • Online scaling

    With just a few clicks on the DCS console, you can scale your instances to a desired capacity with no service downtime (cluster or master/standby instances) or with a minute-level interruption (single-node instances).

  • Data Reliability

    DCS for Redis supports data persistence, backup, and restoration.

  • Security

    Security measures include user identity authentication, VPCs, subnets, security groups, and audit logs.

Data Reliability

  • Data Persistence

    By default, data persistence is enabled for both master/standby and cluster DCS instances. Data is flushed to disk with second-level latency.

  • Data Backup

    You can initiate a manual backup at any time, or create policies to automatically back up data daily during off-peak hours. Each piece of data has three replicas. In the event of a misoperation or if data is corrupted, you can restore your data from a backup in just a few clicks.

Security

  • Network Isolation

    Tenants in different VPCs or security groups cannot access each other or use each other's resources.

  • Traceability

    DCS for Redis works with Cloud Trace Service to record and audit tenant management operations.

  • User Authorization

    DCS for Redis checks password complexity and protects against password cracking. Users must change or reset DCS instance passwords periodically.

  • Metric Monitoring

    You can view more than 30 metrics and customize alarm thresholds and policies.

Metric Monitoring

  • A Wide Range of Metrics

    External Redis metrics include the number of commands, concurrent operations, connections, clients, and denied connections.

    Resource usage metrics include CPU usage, physical memory usage, network input throughput, and network output throughput.

    Internal Redis metrics include instance capacity usage, as well as the number of keys, expired keys, PubSub channels, PubSub patterns, keyspace hits, and keyspace misses.

  • Custom Alarm Thresholds and Policies

    Specify your own alarm thresholds and policies based on monitoring metrics to detect service abnormalities in a timely manner.

Recommended Configurations

Entry-level

2 GB, single-node DCS instance

Entry-level

2 GB, single-node DCS instance

Features

  • Up to 10,000 concurrent connections
  • Flexible scaling
  • Distinctive security features

Scenarios

  • Micro- and small-sized Internet apps
  • Testing environments of small and medium enterprises
¥76.80 /month

Advanced

16 GB, master/standby DCS instance

Advanced

16 GB, master/standby DCS instance

Features

  • HA architecture
  • Data backup and restoration
  • Data persistence

Scenarios

  • Medium-sized Internet apps
  • Production environments of small and medium enterprises
¥1,102.00 /month

Professional

64 GB, master/standby DCS instance

Professional

64 GB, master/standby DCS instance

Features

  • HA architecture with larger capacity
  • Data backup and restoration
  • Data persistence

Scenarios

  • Medium- and large-sized application systems
¥4,544.00 /month
Quick Configuration

Create an Instance

Steps

1. Log in to the DCS console. 2. Click Create Cache Instance. Select instance specifications and configuration. 3. Click OK to create the instance.

Note

DCS instances must run on a Virtual Private Cloud (VPC).

Access an Instance

Steps

1. Using the DCS console, take note of the DCS instance's connection address and the port used. 2. Log in to the ECS console and buy an ECS. Install Redis on the purchased ECS. 3. Use Redis CLI to connect to the DCS instance. Read and write data from and to the instance.

Notes

1. The chosen ECS and the DCS instance must belong to the same VPC. 2. In addition to Redis CLI, you can also use other clients such as Jedis and Credis to access DCS instances.

Migrate Data

Steps

1. Install the data migration tool on the chosen ECS. 2. Export your data files and upload them to the ECS. 3. Import your data files to DCS.

Notes

1. The chosen ECS and the DCS instance must belong to the same VPC. 2. If the source Redis client is not on HUAWEI CLOUD, export your data files to a local PC and upload them to an ECS before importing it to DCS. 3. If the source Redis client is on HUAWEI CLOUD, your data files can be directly exported to ECS and then to the DCS instance. 4. If the source Redis client is on HUAWEI CLOUD but is not in the same VPC as the DCS instance, export your data files to a local PC and upload them to an ECS before importing it to DCS.

Routine Maintenance

Steps

1. Log in to the DCS console. 2. Select a DCS instance that needs routine maintenance.

Notes

1. Exercise caution when restarting a DCS instance, deleting a DCS instance, and changing a password. 2. To verify whether configuration parameter modifications have gone into effect, observe instance performance for a period of time.

Usage Guides

Create an Account and Experience HUAWEI CLOUD for Free

Register Now