Redis

DCS for Redis is a standard, persistent in-memory database service. Based on an HA cluster architecture, it ensures high read/write performance.

Usable Off the Shelf

You can configure and launch cache servers within minutes with just a few clicks, buy on-demand resources, and migrate services to the cloud without any change.

Easy to Use

DCS for Redis supports service migration with little modification and monitors your services based on custom alarm thresholds and policies for over 30 metrics.

Secure and Reliable

Username/password-specific access and audit logs keep your data secure and traceable. The HA architecture provides data persistence and backup mechanisms.

Application Scenarios

  • Gaming

  • E-Commerce

  • Internet

  • Finance

  • Enterprise

Gaming

Gaming

The Redis SortedSet data structure of DCS simplifies leaderboard creation and enables fast access to leaderboards.

Advantages

  • Fast Data Access

    Retrieve frequently accessed 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 loads increase.

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 transferred to disks, maintaining data durability and security.

Related Services

ECS

ELB

Internet

Internet

DCS for Redis is ideal for social and web apps. The Redis Set data structure can maintain data about relationships between friends and the Redis String data structure can cache static 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, resize your DCS instances online to accommodate application load spikes.

Related Services

ECS

ELB

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 security credentials (username and password) and audit logs.

  • Backup and Restoration

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

Related Services

ECS

ELB

OBS

Enterprise

Enterprise

For traditional enterprise apps, a large amount of code is involved and the data processing logic is complicated. Existing relational databases are slow and require optimizations to be performed on-site 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

Functions

Multiple Cache Engines

Choose from Redis or IMDG to suit the needs of your application.

  • 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, hyperlog and geospatial indexes with radius queries. There are three types of DCS Redis instances: single-node, master/standby, and cluster.

  • IMDG

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

High Availability

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

  • Failover

    DCS clients will not perceive the failover because the instance IP address exposed to them remains unchanged.

  • Redundancy

    Redundancy is provided using master and standby instances. For cluster DCS instances, each shard is held on both master and standby nodes.

Flexible Specs

Choose from single-node, master/standby, and cluster instances from 2 GB to 1024 GB.

  • Single-node DCS instances

    Each DCS instance runs on only one cache node and provides 2 GB to 64 GB in storage capacity. These types of DCS instances are recommended only when caching is needed.

  • Master/standby DCS instances

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

  • Cluster DCS instances

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

Scalability

DCS instances scale hitlessly as loads increase.

  • Online scaling

    With just a few clicks on the DCS for Redis console, scale your instances to the needed capacity with no service downtime (cluster or master/standby instances) or minimal interruption at the minute range (single-node instances).

Data Reliability

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

  • Data persistence

    By default, data persistence is enabled for both master/standby and cluster DCS instances. Data is flushed to disks 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 an error in operation or should data become corrupted, you can restore your data from a backup with just a few clicks.

Security

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

  • Network isolation

    Tenants in different VPCs or security groups cannot access each other or use each other's resources, keeping assets segregated and compartmentalized if need be.

  • User authorization

    DCS for Redis checks password complexity and protects against password cracking.

  • Traceability

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

Metric Monitoring

You can view over 30 metrics and customize alarm thresholds and policies.

  • 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 thresholds and alert the specified personnel for such events as frequent keyspace misses, use of expired keys, and other patterns.

Recommended Configurations

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

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

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

Quick Configuration

  • Buy an Instance

  • Access an Instance

  • Migrate Data

  • Routine Maintenance

Buy an Instance

Procedure

1. Log in to the DCS for Redis console.

2. Click Buy DCS Instance, and configure the specifications.

3. After you make the payment, the instance is created.

Note

DCS instances run in Virtual Private Clouds (VPCs).

Access an Instance

Procedure

1. On the DCS console, view the instance's connection address and port number.

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 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

Procedure

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 them to DCS.

3. If the source Redis 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 them to DCS.

Routine Maintenance

Procedure

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 that modifications to configuration parameters have taken effect, observe instance performance for a reasonable period of time.