Accelerate Your Apps with Alibaba Cloud Tair (Redis): A Complete Deployment Guide

1. Introduction

Cloud Database Tair (Redis compatible) is a database service compatible with the open‑source Redis protocol, suitable for caching and real‑time stream processing. It offers stability, elastic scaling, and ease of use. To reduce response time and improve performance, caching is the primary solution.

2. Deployment Preparation

2.1 Prepare Account

If you do not have an Alibaba Cloud account, register one and ensure the account balance is at least ¥100 for pay‑as‑you‑go resources.

2.2 One‑Click Deploy Resource Stack

Open the one‑click configuration template link, which opens the ROS console and displays the YAML template.

Confirm the region, keep default options, and click Next.

On the parameter page, modify the stack name, select an availability zone, and configure an ECS instance (e.g., c6.large). Fill all required fields and click Create.

When the stack status shows “Create Success”, the deployment is complete.

After deployment, call the initialization API to import mock data.

3. Course Content

3.1 Verify Cache Functionality

After deployment, access the application API via the ECS public IP and compare responses with and without cache.

Test the non‑cached interface:

http://<ECS_IP>/getAllEmployeesInDepartment?departmentId=1&cacheFirst=false

Test the cached interface:

http://<ECS_IP>/getAllEmployeesInDepartment?departmentId=1&cacheFirst=true

Observe that the cached response contains a message field indicating the data was read from cache.

3.2 Performance Test with Locust

Use Locust to simulate high concurrency and monitor database pressure.

Create locustfile.py with test scenarios.

Run locust and open the web UI to start the test.

Stop the test after a period and view RDS monitoring metrics.

Comparison shows that without cache the execution count peaks near 700, while with cache it stays in single digits, demonstrating that caching alleviates database load.

3.3 Verify Cache Hit After Deleting Data

Delete records from the Redis instance, then access the cached API again. The response still contains the message indicating a cache hit, confirming correct cache behavior.

4. Clean Up Resources

Delete the created ECS instance, VPC, switch, RDS MySQL instance, and Redis instance to avoid further charges.