Tablestore:Overview

Background information

Tablestore is a table-based low-cost serverless storage service that can be used to store large volumes of structured data. Tablestore allows you to query and retrieve online data within milliseconds and perform multi-dimensional analysis on stored data. Tablestore is suitable for scenarios such as billing, instant messaging (IM), Internet of Things (IoT), Internet of Vehicles (IoV), risk control, and intelligent recommendation. Tablestore provides a deeply optimized one-stop storage solution for IoT applications. For more information, see What is Tablestore?

OSS is a secure, cost-effective, and highly reliable cloud storage service. OSS allows you to store large amounts of data in the cloud. OSS provides multiple storage classes to help you manage and reduce storage costs. For more information, see What is OSS?

DataWorks is an end-to-end big data development and governance platform that provides data warehousing, data lake, and data lakehouse solutions with big data compute engines, such as MaxCompute, Hologres, E-MapReduce (EMR), AnalyticDB, and CDP. Data Integration is a stable, efficient, and scalable data synchronization service. It can be used to quickly and stably migrate and synchronize data among a wide range of heterogeneous data sources that reside in complex network environments. For more information, see Data Integration.

Scenarios

• Tablestore: provides a professional data-persistent storage service and user-oriented real-time read/write operations with high concurrency and low latency.

• OSS: supports backup at an extremely low cost.

Usage

• Full export

  Export full data from Tablestore to OSS. For more information, see Export full data by using the code editor.

• Synchronize incremental data

  Synchronize incremental data from Tablestore to OSS. For more information, see Synchronize incremental data in script mode.

Limits

• Write by whole row

  Tablestore Stream requires that a whole row of data be written to Tablestore each time. Currently, the whole-row data write mode is applied to the writing of time sequence data such as IoT data. Therefore, data cannot be modified after it is written.

• Synchronization latency

  Currently, periodic scheduling is used when incremental data is synchronized, and the scheduling interval is 5 minutes. The plugin has a synchronization latency of 5 minutes and the total latency of a synchronization task is 5 to 10 minutes.

Prerequisites

• OSS is activated, and a bucket is created. For more information, see Activate OSS and Create buckets.

• The instance and table information to be synchronized from Tablestore to OSS is confirmed and recorded.

• DataWorks is activated, and a workspace is created. For more information, see Activate DataWorks and Create a workspace.

• A RAM user is created and is granted full OSS management permissions (AliyunOSSFullAccess) and Tablestore management permissions (AliyunOTSFullAccess). For more information, see Create a RAM user and Grant permissions to the RAM user.

  Important

  To prevent security risks caused by the leakage of the AccessKey pair of your Alibaba Cloud account, we recommend that you create a RAM user.

• An AccessKey pair is created for the RAM user. For more information, see Create an AccessKey pair.