| Basic Configuration |
Region |
The region where you want to create an ApsaraDB for Redis instance. You cannot change
the region after the instance is created.
- To maximize access speed, we recommend that you select a region that is close to the
geographic location of your users.
- To enable connections over an internal network, make sure that the ApsaraDB for Redis
instance is deployed in the same region as an Elastic Compute Service (ECS) instance.
Otherwise, the instances can communicate with each other only over the Internet. Connections
over the Internet may degrade the service performance.
|
| Zone |
Select a zone that belongs to the region. Each region has multiple isolated locations
that are known as zones. Each zone has its own independent power supply and network.
An ECS instance and an ApsaraDB for Redis instance in the same zone can be interconnected
over the internal network with the minimum network latency.
Note To implement zone disaster recovery, you can deploy the ApsaraDB for Redis instance
across multiple zones.
|
| Network Type |
- VPC: A virtual private cloud (VPC) is an isolated network with higher security and better
performance than a classic network. We recommend that you select the VPC network type.
- Classic Network: Cloud services in the classic network are not isolated. Access control to cloud
services in a classic network is implemented by the security groups or whitelist policies
of the services.
Notice
- To enable connections over an internal network, make sure that the ApsaraDB for Redis
instance is connected to the same type of network as an ECS instance or an ApsaraDB
for RDS instance.
- If only the VPC network type is used to enable connections, make sure that the ApsaraDB
for Redis instance is connected to the same VPC as the ECS instance or ApsaraDB for
RDS instance.
- You can change the network type of ApsaraDB for Redis instances from Classic Network to VPC. However, you cannot change the network type from VPC to Classic Network.
|
| VPC |
Select a VPC in which you want to create the ApsaraDB for Redis instance. For more
information about VPC, see . |
| VSwitch |
Select a VSwitch for the VPC. If no VSwitches are created for the VPC in the current
zone, see . |
| Instance |
Edition |
- Community Edition: This edition is compatible with the Redis protocol and provides database solutions
that support hybrid storage in memory and disks.
- Enhanced Edition (Tair): This edition is developed based on ApsaraDB for Redis Community Edition. It is optimized
in terms of performance, storage, and data schemas. For more information, see Overview.
|
| Series |
If you select Enhanced Edition (Tair) as Edition, you have the following series options:
- Enhanced Performance: uses a multi-threading model. The performance of this series is three times that
of a Community Edition instance of the same specification. It also provides multiple
data schema modules to simplify development. For more information, see .
- Hybrid Storage: integrates the benefits of the in-memory and on-disk persistence. This series can
reduce the usage cost and allows you to maintain a proper balance between the performance
and cost. For more information, see Hybrid-storage instances.
|
| Version |
The engine version of the ApsaraDB for Redis instance.
Note The instances that run Redis 2.8 will soon be phased out. We recommend that you create
an instance that uses the latest database version to use more features and achieve
stable performance.
|
| Architecture Type |
- Cluster: resolves the performance bottleneck that is caused by a single-threading model.
You can use the instances to process large-capacity or high-performance workloads.
- Standard: runs in a master-replica architecture, and provides high-performance caching services
and high data reliability.
- Read-Write Splitting: ensures high availability, high performance, and supports multiple specifications.
The read/write splitting architecture allows a large number of concurrent requests
to read hot data from read replicas. This can reduce the loads on the master node
and minimize your costs of operations and maintenance.
For more information, see Overview.
|
| Shards |
Specifies the number of shards for the Redis cluster instance. Data is distributed
across the shards in the cluster.
Note This parameter is supported only when you set Architecture Type to Cluster.
|
| Node Type |
- If you set Architecture Type to Cluster or Standard, Master-Replica is the only available option. This dual-node hot-standby architecture provides data
persistence with high data reliability and availability.
- If you set Architecture Type to Read-Write Splitting, you can choose the node type based on the number of read-only replicas.
|
| Instance Class |
Each instance type contains a group of configurations, such as the memory capacity,
maximum number of concurrent connections, and maximum internal bandwidth. For more
information, see Overview.
Note The database metadata is generated after you create an ApsaraDB for Redis instance.
The size of the metadata on each shard of cluster instances is 30 MB to 50 MB. The
total size of the metadata for a cluster equals the sum of the size of metadata on
each shard of the cluster.
|
| Password Setting |
- Later: Set the password after the instance is created. For more information, see Change the password.
- Now: Enter the password for the instance.
- The password must be 8 to 32 characters in length.
- The password must contain at least three of the following types of characters: uppercase
letters, lowercase letters, digits, and special characters.
- Special characters include
(!) @ # $ % ^ & * ( ) _ + - =
|
| Purchase Plan |
Instance Name |
The name of the instance allows you to identify and manage the instance. |
| Quantity |
Specify the number of instances with the same configuration that you want to create.
You can create up to 99 instances.
|
| Duration |
When you select a Subscription billing method, you must specify the duration and select whether to enable auto renewal.
|