Preface
TcaplusDB is a distributed NoSQL database specially designed for games. As part of Tencent Cloud's database service, it provides customers with the ultimate game data experience. At present, it has provided stable data storage services for tens of millions of DAU masterpieces such as "King of Glory", "Crossing the Line of Fire" and "Naruto". Relying on Tencent Cloud, it covers five continents (Asia, Europe, North America, South America, Oceania) ) Basic equipment service node, game developers only need to access once to facilitate the global game user experience.
One, TcaplusDB architecture
Figure 2.1 TcaplusDB architecture diagram
1 Introduction
TcaplusDB is a distributed NoSQL database specially designed for games. As part of Tencent Cloud's database service, it provides customers with the ultimate game data experience. At present, it has provided stable data storage services for tens of millions of DAU masterpieces such as "King of Glory", "Crossing the Line of Fire" and "Naruto". Relying on Tencent Cloud, it covers five continents (Asia, Europe, North America, South America, Oceania) ) Basic equipment service node, game developers only need to access once to facilitate the global game user experience. Specific product information, please refer to the official website link .
2. TcaplusDB architecture
[External link image transfer failed. The source site may have an anti-leech link mechanism. It is recommended to save the image and upload it directly (img-KLX71Pmb-1612696762770)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01 /1.png)]
Figure 2.1 TcaplusDB architecture diagram
| serial number | Component name | description |
|---|---|---|
| 1 | Tcapcenter | Process requests from web pages, and manage each node of the entire Tcaplus cluster as zookeeper. |
| 2 | Tcaproxy | The access layer receives the request from the SDK/API, interacts with the Master node, obtains the return information of the Master node, and then returns to the SDK/API requester. |
| 3 | Tcapdir | Directory server. Store and maintain the node information of the Tcaproxy cluster, and respond to requests from SDK/API to query Tcaproxy node information (IP address and service port). |
| 4 | Tcapsvr-Master | The master node of the storage layer stores data fragments and is responsible for responding to Tcaproxy requests. |
| 5 | Tcapsvr-Slave | The backup node of the storage layer stores the backup data and backs up the master node data in real time. When the Master node fails, it will be upgraded as the Master node. When it is the backup node, it will not communicate with Tcaproxy. |
| 6 | Backup Center | Cross-city/regional cold backup center. The cold backup center is deployed in a data center remote from the Master node. It performs cold backup of storage layer data from the Slave node on a daily basis, and performs Binlog log backup from the Slave node every 15 minutes. |
| 7 | Data Analysis | Responsible for exporting the structured data in TcaplusDB, see 6.2. |
3. TcaplusDB technical principle
3.1 Storage principle
A table is divided into tables through HASH, and modulo sharding is performed according to the length of the routing array (the default is 10k), so each table can be divided into up to 10k shards (Shard). The following figure is an example. A TcaplusDB table is divided into 5 shard files and distributed to different storage nodes. Each node has 1 or more shards of data.
[External link image transfer failed. The source site may have an anti-leech link mechanism. It is recommended to save the image and upload it directly (img-DJVBDElk-1612696762774)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01 /2.png)]
Figure 3.1 Schematic diagram of TcaplusDB storage technology
3.2 System expansion
The expansion of TcaplusDB is carried out at the storage layer and the access layer. From the architecture diagram in Chapter 2, you can see that the access layer is the Tcap Proxy layer, and the storage layer is the Tcapsvr layer (active and standby nodes). For the access layer, it adopts a stateless design, so it can scale flexibly and horizontally, without affecting online business, and has no perception of business; for the storage layer, because the table adopts a fragmented design, When expanding the capacity, it is necessary to horizontally migrate the shards on the original machine to the new machine to achieve the purpose of expanding the storage space. Take Figure 3.2 as an example. Before the expansion of Table A, there is only one shard Shard 1, and the length of the routing array is 10k. During expansion, the table is divided into two shards, where routing items 0-5k are placed on Shard1, routing items 5001-10k are placed on Shard2, and the two shards are stored on two storage nodes respectively.
[External link image transfer failed. The source site may have an anti-leech link mechanism. It is recommended to save the image and upload it directly (img-kouFTJF9-1612696762774)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01 /3.png)]
Figure 3.2 Schematic diagram of storage node expansion
The data migration process is shown in Figure 3.3. The data on the original TcaplusDB Salve node will be copied to the new TcaplusDB Master node. The data integrity is maintained through binlog synchronization. The data request of the access layer tcapoxy is redirected to the new TcaplusDB cluster.
[External link image transfer failed. The source site may have an anti-leech link mechanism. It is recommended to save the image and upload it directly (img-ZMGHC5t2-1612696762777)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01 /4.png)]
Figure 3.3 Diagram of request redirection after expansion
Access layer expansion, as shown in Figure 3.4, through consistent hash routing switching, the original four tcaproxy forwarding routes are equally distributed to five tcaproxy, and the routing switching process will not cause message loss.
[External link image transfer failed. The source site may have an anti-leech link mechanism. It is recommended to save the image and upload it directly (img-cAgviWZe-1612696762779)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01 /5.png)]
Figure 3.4 Schematic diagram of access layer expansion
The expansion of TcaplusDB is based on the two dimensions of storage node disk usage and QPS (Queries per Second). When the capacity usage of a single storage node reaches a certain threshold, the expansion operation is triggered.
3.3 TcaplusDB availability and consistency
3.3.1 High availability
The TcaplusDB component adopts high-availability deployment by default:
- The management node tcapcenter is deployed in the Master/Slave mode, and automatically switches to the Slave when the Master fails.
- The management node tcapdir will deploy multiple processes.
- The access layer tcaproxy adopts a redundant method, and the failure of a single access layer node will not cause abnormal user request processing.
- The storage layer tcapsvr adopts the Master/Slave mode, and the master-slave switching is lossless. The storage layer tcapsvr Master/Slave and the access layer tcaproxy deployment preferentially adopt intra-city and cross-computer room deployment, and also support cross-rack, cross-switch, and cross-floor deployment.
3.3.2 Disaster recovery
The TcaplusDB API maintains a consistent Hash ring. When the access layer nodes are added or reduced, the TcaplusDB API will automatically adjust the tcaproxy information of the access layer.
- Access layer abnormality : TcaplusDB will send heartbeats to the access layer tcaproxy every second. If the access layer node does not return a response within 10s, the TcaplusDB API will proactively mark the node as unavailable and use other nodes.
- Storage layer abnormality : When the tcapsvr Slave is abnormal, it will be replaced by a new Slave node. If an exception occurs in the tcapsvr master, Slave will switch to Master, and the user request during the switching process fails. It is recommended that developers add retry logic code. Master/Slave supports sub-health switching. When the read and write error rate reaches the threshold (80% by default), the master-slave switch will be performed, as shown in the following figure:
[External link image transfer failed. The source site may have an anti-leech link mechanism. It is recommended to save the image and upload it directly (img-mHnbpM9q-1612696762780)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01 /6.png)]
Figure 3.5 Schematic diagram of disaster recovery
Both the access layer tcaproxy and the storage layer tcapsvr have overload protection. Requests that exceed the reserved read and write will trigger an error code to return.
3.3.3 Data consistency guarantee
For TcaplusDB, there are complete data consistency guarantee measures, as follows:
- Normal read and write scenarios : The master and backup use binlog to ensure data consistency. The master and backup will execute the binlog in a strict and consistent time sequence; the time difference between the master and backup is about 10ms; business read and write requests are executed on the master node.
- Active /standby switchover : The active switchover of the system will first wait for the data to be fully synchronized before switching. If the failover process no longer exists, about 10ms of data may be lost. At this time, the old request is still connected to the original master. The TcaplusDB master-slave synchronization currently uses an asynchronous write mechanism. When the data is written to the master process, it may fail. The data will be disconnected before the synchronization of the backup machine in the future. At this time, the data may be lost. The current internal and external customers are still in the acceptable range of this loss and will not cause much impact on the business. In view of this situation, the project team is also planning to design a strong synchronization mechanism to ensure that data will not be lost, but it will sacrifice a certain amount of throughput.
- Periodic primary and backup data consistency full comparison : According to user needs, the full data consistency comparison is done during low peak periods. During the comparison process, due to the inconsistency of the front-end read and write products, it will automatically judge and repeat the verification based on the record modification time to discover the potential inconsistency risk of the system. The usual practice is to spot check some data fragments of some core tables for full comparison to ensure comparison efficiency.
- Cold standby data consistency guarantee : When the standby node is doing full cold standby, all data files are in a completely static state at the beginning of the cold standby. At this time, all data is backed up by byte copy, and there is no consistency problem. And during the cold standby period, the front-end read and write are not affected at all, new requests will be written into a small modification set, and the request will merge the full amount of data and the small modification set.
- Data landing security guarantee : Business data has a CRC check when the storage node is landed. If the data is tampered with, the CRC check will fail, and incorrect data will not be returned to the user.
3.4 Backup and recovery
3.4.1 Cold standby
At present, TcaplusDB supports two methods of data backup: cold backup of full data files, scheduled daily, after the table is created, there will be scripts to automatically backup and store the data files, the full backup file storage period is 25 days; the other is incremental backup , Mainly based on the binlog of TcaplusDB, once every 15 minutes, and the incremental pipeline storage period is 15 days. Through the combination of the two methods of backup, the ability to quickly recover through the backup during the abnormal period of the system is guaranteed.
3.4.2 Back file
TcaplusDB's back file supports two methods:
| Retracement method | description | Support method |
|---|---|---|
| Cold standby | Use the backup file to revert to the time point of the cold standby, accurate to the millisecond. | Temporarily support through work orders |
| Precise retracement | Use the backup file and binlog file to return to any specified time point, accurate to the millisecond. | Temporarily support through work orders |
Cold standby and precise retracement support the following 4 types of retracement ranges:
| Retracement range | description | Support method |
|---|---|---|
| Full server back file | All tables are backed up | Temporarily support through work orders |
| Single table rollback | Only a single table is backed | Temporarily support through work orders |
| Log back | To file a single record, specify the KEY when you file the file. | Tencent Cloud console support |
| Conditional retracement | Specify the filter criteria to file back, such as specifying the key to be filed back | Temporarily support through work orders |
3.5 performance tuning
The access layer tcaproxy responds to and processes requests by default using Memory Pool technology, thereby reducing memory usage.
The storage layer tcapsvr uses the Google snappy compression algorithm, which saves about 30% of storage space. Expired data can be eliminated according to the configured expiration time and table name.
Each server of the storage layer tcapsvr runs in a single process and consists of 36 threads, including the main thread, 30 worker threads, LRU threads, master-slave synchronization threads, data migration threads, slow write threads, and Binlog flushing threads. The 30 working threads are divided into fast and slow threads. For example, get (search by primary key), replace (update), etc. are processed by fast threads, and getbypartkey (search by index), etc., are processed by slow threads. Through the functional division of different threads, the processing efficiency is improved.
3.6 Monitoring indicators
TcaplusDB supports email, WeChat and phone alarms. Common alarm monitoring indicators are as follows:
| index | description |
|---|---|
| General error rate | The ratio of the number of requests caused by user errors to the total number of requests |
| System error rate | The ratio of the number of error requests to the total number of requests caused by a TcaplusDB error in the storage layer node |
| Average error rate | The number of error requests (the sum of the number of general errors and the number of system errors) as a percentage of the total number of requests |
| Actual read capacity unit | Read CU, 1 read CU is a 4KB read operation |
| Actual write capacity unit | Write CU, 1 write CU is a 4KB write operation |
| Average read latency | Average latency of all read requests in 60 seconds |
| Average write latency | Average latency of all write requests in 60 seconds |
| storage capacity | Stored data size (GB) |
3.7 System Security
- Network security : The TcaplusDB environment is currently in the Tencent Cloud VPC private network environment, and it is fully isolated from the outside world to ensure user data security.
- Access security : Mainly reflected in several aspects:
- CAM : TcaplusDB currently integrates Tencent Cloud user authority management system CAM, which supports interface-level authority access control to prevent non-related personnel from accessing data;
- Access password : TcaplusDB application creation needs to set an access password, which is used for authentication of the directory server tcapdir and the access layer server tcaproxy;
- IP whitelist : TcaplusDB backend supports access based on IP whitelist, that is, designated IP clients to read and write TcaplusDB data;
- Audit : All user operations have audit logs, so that all visits are well documented.
- Data security : serialization and deserialization operations will be used after data read and write compression or decompression, even if the data file is hijacked, the data content cannot be parsed
- Compliance and security : Data files will be encrypted with aes-128-cbc to meet EU GDPR standards; at the same time, Tencent Cloud also provides a large number of foreign security certification systems, such as South Korea’s KIMS, for many customers who need to go overseas.
4. TcaplusDB operation
4.1 Table definition
TcaplusDB supports 2 types of tables, protobuf (Protocol Buffers) table and TDR (Tencent Data Representation) table. Protobuf is a descriptive language developed by Google that serializes structured data while emphasizing simplicity and performance; TDR is a cross-platform data representation language developed by Tencent, which combines XML, binary and ORM (Object Relational Mapping) The advantage of is widely used in the serialization scene of Tencent game data.
4.1.1 Protobuf 表
The following is game_players.protoan example of the protobuf table . You can upload the file to the Tencent Cloud console and create the table.
syntax = "proto3"; // Specify the protobuf language version, proto3.
// Import TcaplusDB public definition service
import "tcaplusservice.optionv1.proto";
message game_players {// Define TcaplusDB table, including message type
// Create a primary key field based on the selection tcaplusservice.tcaplus_primary_key
// TcaplusDB can specify up to 4 primary key fields in a single table
option(tcaplusservice.tcaplus_primary_key) = "player_id, player_name, player_email";
// 基于选择项tcaplusservice.tcaplus_index创建主键索引
option(tcaplusservice.tcaplus\_index) = "index\_1(player\_id, player\_name)";
option(tcaplusservice.tcaplus\_index) = "index\_2(player\_id, player\_email)";
// TcaplusDB支持的数值类型:
// int32, int64, uint32, uint64, sint32, sint64, bool, fixed64, sfixed64, double, fixed32, sfixed32, float, string, bytes
// 嵌套类型: message
// 主键字段
int64 player_id = 1;
string player_name = 2;
string player_email = 3;
// 普通(非主键) 字段
int32 game\_server\_id = 4;
repeated string login_timestamp = 5;
repeated string logout_timestamp = 6;
bool is_online = 7;
payment pay = 8;
}
message payment {
int64 pay_id = 1;
uint64 amount = 2;
int64 method = 3;
}
4.1.2 TDR table
TDR supports general ( generic) table and list ( list) table. The generic table is a table that represents element attributes in the form of a table, such as students, employers, and game players. The list table is a series of records, such as game leaderboards, in-game emails (usually the most recent 100 emails).
It is recommended to create two different types of tables in one XML file.
- The element metalib is the root element of the xml file. In addition, you can use union to create nested types:
- The attribute tagsetversion should always be 1.
- The struct element containing the attribute primarykey defines a table; otherwise, it is just a normal structure.
- Every time the table structure is modified, the version attribute value needs to be increased by 1, and the initial version is always 1.
- The primarykey attribute specifies the primary key field; for the generic table, you can specify up to 4 primary key fields, and for the list table, you can specify three.
- The splittablekey attribute is equivalent to the shard key, and the TcaplusDB table is split and stored in multiple storage nodes. The splittablekey must be one of the primary key fields. A good splittablekey should be highly dispersed, which means that the value range is very wide. It is recommended to use the string type.
- The desc attribute contains the description of the current element.
- The entry element defines a field. The supported value types include int32, string, char, int64, double, short, etc.
- The index element defines an index, which must contain splittablekey. Since the primary key can be used to query the table, the index should not be the same as the primary key attribute. Example:
users_mails.xml
<!-- generic_table `users`, store the user’ information -->
<!-- an user may has many roles -->
<entry name="level" type="int32" defaultvalue="1" desc="role's level"/>
<entry name="role_name" type="string" size="1024" desc="role's name"/>
<entry name="last\_login\_time" type="string" size="64" defaultvalue="" desc="user login timestamp"/>
<entry name="last\_logout\_time" type="string" size="64" defaultvalue="" desc="user logout timestamp"/>
<index name="index1" column="user_id"/>
<!-- list_table `mails`, store the role’s mails -->
<entry name="text" type="string" size="2048" desc="mail text"/>
<entry name="send_time" type="string" size="64" defaultvalue="" desc="timestamp of the mail sent"/>
<entry name="read_time" type="string" size="64" defaultvalue="" desc="timestamp of the mall read"/>
- The union element contains a collection of primitive types, such as integers and strings. Union can also be referenced as a custom type;
- The Macro tag is used to define constants.
4.2 TcaplusDB client
Download the latest TcaplusDB API 3.36 package and unzip the file. You should perform all operations on the CVM in the same VPC of the TcaplusDB application. Download link : TcaplusServiceApi3.36
# Decompress the TcaplusDB API package
tar -zxvf TcaplusServiceApi3.36.0.192960.x86_64_release_20200115.tar.gz
# Rename the TcaplusDB directory
mv TcaplusServiceApi3.36.0.192960.x86_64_release_20200115 TcaplusDBServiceApi3.0
# Find the TcaplusDB client
cd TcaplusDBServiceApi3.0/release/x86_64/bin
# Connect the TcaplusDB application./tcaplus_client
-a {APP ID} -z {ZONE ID} -s {TcaplusDB PASSWORD} -d {Tcapdir IP}:{Tcapdir PORT}
# Example:
./tcaplus_client -a 21 -z 1 -s “Changeme12” -d 10.0.0.2:9999
The above-mentioned TcaplusDB_client connection parameter acquisition method is as follows:
1) Open the table console, enter the cluster list page , obtain Tcapdir IP (corresponding: Private Address/intranet address), Tcapdir PORT (corresponding: Private Port/intranet port), and obtain Zone ID (corresponding page: Table Group ID/table group ID).
[External link image transfer failed. The source site may have an anti-leech link mechanism. It is recommended to save the image and upload it directly (img-zIS2cjfy-1612696762781)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01 /7.png)]
Figure 3.6 Get connection parameters
2) Click the cluster ID in the above screenshot to enter the application details page, and obtain the APP ID (corresponding: Access ID/access ID), and TcaplusDB password (corresponding: Connection Password/connection password). The specific screenshot is as follows:
[External link image transfer failed. The source site may have an anti-leech link mechanism. It is recommended to save the image and upload it directly (img-nX9OQR2E-1612696762781)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01 /8.png)]
Figure 3.7 Get connection parameters
4.3 TcaplusDB client commands
TcaplusDB provides a SQL-like query language that enables you to manipulate TcaplusDB tables like a relational database.
| command | meaning |
|---|---|
| desc {table name} | Description table field |
| count {table_name} | Return the number of table records |
| clean {table_name} | Empty (truncate) table, this operation is highly sensitive and needs to be used openly |
| select | 查询表记录,示例: select * from BattleInfo where game_id = 100 and area_id=200 \G; \G标记符类似MySQL命令行格式化查询输出 |
| update | 更新表记录，若该记录不存在，则会插入该条记录，示例: update BattleInfo set player_number = 10 where game_id = 100 and area_id=200; |
| delete | 删除1条或多条记录，where语句需指定全部主键字段或索引字段。示例: delete from BattleInfo where game_id = 100 and area_id=200; |
| dump | 遍历表并将数据导出到文本文件，示例:dump * from BattleInfo into BattleInfo.csv; |
| load | 从文本文件导入数据到表，示例:load BattleInfo from BattleInfo.csv; |
注意: 使用tcaplus_client在操作PB类型(protobuf)的表时有一些限制，如下所示:
- load: 不支持, 预计Q2支持;
- select: 部分不支持，预计Q2支持，如下:
- 基于索引字段作为where查询条件暂不支持;
- select *不支持显示嵌套字段的值, 需要用点分模式指定嵌套字段才行如select pay.amount from …;
- update: 部分不支持，对于repeated类型的字段无法用update 更新插入;
- insert: 暂不支持, 可用update替代，预计Q2支持。
您可以通过运行help或help +命令获得更多的TcaplusDB语法。 请注意，上表中未列出的命令正在逐步淘汰或不建议使用。
[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-yDZMpW21-1612696762783)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01/9.png)]
图3.8 tcaplus_client命令支持详情
[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-DsjZmWfp-1612696762783)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01/10.png)]
图3.9 tcaplus_client命令帮助示例
5. TcaplusDB限制条件
| 编号 | 资源 | 上限 |
|---|---|---|
| 1 | 单表格组允许表格数 | 256 |
| 2 | 分标键(shard键) | 1 |
| 3 | 单表的Shard数 | 10,000 |
| 4 | 单shard大小 | 256GB |
| 5 | 单表大小 | 2.56PB |
| 6 | generic表主键字段 | 4 |
| 7 | generic表非主键字段 | 128 |
| 8 | list表组件字段 | 3 |
| 9 | list表非主键字段 | 127 |
| 10 | list表中的记录数 | 1024 |
| 11 | 表索引 | 8 |
| 12 | 字段长度(亦称属性长度) | 32B |
| 13 | 主键字段长度 | 1KB |
| 14 | 非主键字段长度 | 256KB |
| 15 | 单记录大小 | 1MB |
| 16 | 单索引关联记录数 | 无限制 |
| 17 | 单表允许分布的表格组数 (同一个表允许分布在一个表格组也可以分布在多个表格组) | 8 |
| 18 | 批量查询返回记录数 | 1024 |
6. API_Explorer使用
腾讯云提供了一个API在线使用的平台:API 3.0 Explorer。通过这个平台，用户可以方便在线测试对应产品的API接口调用逻辑。目前支持Java,Python, Node.js, PHP, Go和.Net等开发语言API ，只需在页面选择对应的API接口方法，填入对应方法参数后，定位到“在线调用”页面点击“发送请求”即可在线返回API的调用结果。API Explorer 支持两种方式API调用：一种是根据输入参数自动生成对应语言的调用代码，可以把这些代码放到自己的云环境机器中调用，方便更灵活的使用API; 另一种是根据输入参数自动生成Http调用代码，可直接在云环境机器用curl方式调用获取API返回结果。这里介绍下如何通过API Explorer来操作TcaplusDB及获取TcaplusDB表监控指标数据, 关于TcaplusDB表操作相关API请参考:TcaplusDB API, 关于监控数据获取API请参考:Monitor API。下面介绍下通过API Explorer 获取TcaplusDB表监控数据的例子。
调用代码生成如下：
[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-DnFVJpYy-1612696762784)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01/11.png)]
图3.10 获取监控数据示例
调用返回结果如下：
[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-7goV7H4o-1612696762784)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01/12.png)]
图3.11 返回结果示例
7. 技术支持
7.1 问题升级
[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-oXljTgMH-1612696762785)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01/13.png)]
图3.12 升级流程
7.2 报表支持
7.2.1 导出到关系型数据库
TcaplusDB支持用户选择部分Table的明文字段实时导入Mysql等关系型数据库，使用SQL语句查询和分析。
实现原理如下图所示：
[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-f7yS4lqt-1612696762786)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01/14.png)]
图3.13 导出MySQL示例
7.2.2 导出文本文件
TcaplusDB支持通过数据导出工具直接导出数据到JSON文件, 同上面用tcaplus_client导出csv文件类似。
[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-Wye31vi0-1612696762786)(https://tcaplusdb.tencent.com/wp-content/uploads/2021/01/15.png)]
图3.14 导出JSON文件
8. 附录
8.1 TcaplusDB 新旧术语对比和使用场景
| 编号 | 旧术语 | 使用场景 | 新术语 | 使用场景 |
|---|---|---|---|---|
| 1 | Application | 仅适用TcaplusDB Client | Cluster | TcaplusDB云控制台 |
| 2 | Deployment Unit (Zone) | 仅适用TcaplusDB Client | Table Group | TcaplusDB 云控制台 |
| 3 | Application ID | 仅适用TcaplusDB Client | Cluster ID | TcaplusDB云控制台 |
| 4 | Deployment Unit ID (Zone ID) | 仅适用TcaplusDB Client | Table Group ID | TcaplusDB 云控制台 |
| 5 | app_id | 仅适用TcaplusDB Client | access_id | SDK中关于CRUD操作部分 |
| 6 | app_pwd | 仅适用TcaplusDB Client | access_passwd | SDK中关于CRUD操作部分 |
| 7 | zone_id | Only applicable to TcaplusDB Client | table_group_id | The CRUD operation part of the SDK |