This topic describes the terms in Lindorm.


security group

A security group is a virtual firewall that is used to manage the inbound and outbound traffic of Elastic Compute Service (ECS) instances in the security group. After a security group is added to the whitelist of a Lindorm instance, the ECS instances in the security group can access the Lindorm instance. For more information, see Add a security group.


You are charged on an hourly basis. For short-term use, we recommend that you select the pay-as-you-go billing method. If you no longer require a pay-as-you-go instance, you can release the instance to reduce costs. .



You are charged a subscription fee when you create an instance. In most cases, the subscription billing method is more cost-effective than the pay-as-you-go billing method for long-term use. You are provided a larger discount for a longer subscription duration.

local SSD

Local SSDs are SSDs that are deployed on the same node as the database engine to which the SSDs are attached. You can store data on local SSDs to reduce I/O latency. For more information, see Storage types.


CPU utilization

CPU utilization indicates the CPU resources that are occupied by the programs and processes in a database system in a specific period of time.



Lindorm supports various data models such as wide tables, time series, objects, files, queues, and spatialtemporal data models. Lindorm supports standard SQL and open source interfaces. Engines that store data in the data models can access each other. This helps make application development more agile, flexible, and efficient.


Data Management (DMS) is a database management service that integrates the following features: data management, structure management, user authorization, security auditing, data trend analysis, data tracking, BI charts, performance optimization, and server management. For more information, see What is DMS?.


Alibaba Cloud Data Transmission Service (DTS) supports data transmission between data sources such as relational databases (SQL), non-relational databases (NoSQL), and online analytical processing (OLAP) databases. DTS provides the following features: data synchronization, data migration, change tracking, data integration, and data processing. This helps you build a secure, scalable, and highly available architecture. For more information, see What is DTS?.

dedicated specification

A dedicated instance exclusively occupies all CPU and memory resources that are allocated. The performance of a dedicated instance remains stable and is not affected by other instances that are deployed on the same physical machine. The maximum dedicated specification is that all resources of a physical machine are exclusive to the dedicated specification.


A region refers to a geographical location where the servers of Lindorm instances are deployed. You must specify a region when you purchase a Lindorm instance. The region cannot be changed after the Lindorm instance is purchased.

dynamic column

Dynamic columns are supported by the wide table engine of Lindorm. Dynamic columns are columns that can be dynamically added based on your business requirements without the need to pre-define columns. For more information, see Manage dynamic columns.


A Lindorm instance can be deployed in multiple zones. This deployment solution provides better disaster recovery capabilities for the instance. If the consistency level of a Lindorm wide table is eventual consistency, the Lindorm instance automatically routes requests between multiple zones. This improves the anti-jitter capability of your business in a single zone. For more information, see Cross-zone deployment.



Elastic Compute Service (ECS) is an easy-to-use, efficient, and scalable computing service provided by Alibaba Cloud. ECS helps you build more stable and secure applications, improve O&M efficiency, reduce IT costs, and enable you to focus more on core business innovation. For more information, see What is ECS?.

enhanced SSD (ESSD)

Alibaba Cloud ESSDs use 25 Gigabit Ethernet and remote direct memory access (RDMA) to reduce latency and provide up to 1,000,000 random read/write IOPS per disk. For more information, see ESSDs.

secondary index

Multiple secondary indexes can be created for a wide table of a Lindorm instance in the Tabular model. Secondary indexes are non-primary key indexes. In query scenarios in which non-primary keys are matched, secondary indexes can help reduce the complexity of application development, ensure data consistency, and improve write efficiency. For more information, see High-performance native secondary indexes.


Lindorm Ganos

Ganos is a spatiotemporal big data engine system that is launched by Alibaba Cloud. Ganos is used to manage spatial geometric data and spatiotemporal trajectories. Lindorm Ganos is compatible with open source GeoMesa and GeoServer ecosystems. Lindorm Ganos provides efficient built-in algorithms, such as algorithms for spatiotemporal indexing and geometric algorithms for calculating topological spaces. You can use Lindorm Ganos together with the wide table engine of Lindorm and the serverless Spark engine in Data Lake Analytics (DLA). This allows distributed storage and data analysis. Lindorm Ganos is suitable for multiple scenarios. You can use Lindorm Ganos to store, query, analyze, and mine large amounts of data, including spatial data and spatiotemporal data. For more information, see Overview of Ganos.



I/O is short for input and output. I/O indicates the read and write operations that are performed on a disk.


IOPS indicates the number of read and write operations that are performed to read and write 4 KB of data on a block storage device per second.

IP address whitelist

An IP address whitelist is a list of IP addresses from which access requests can be sent to the Lindorm instance. You can configure IP address whitelists for Lindorm instances to implement high-level access control and security protection for the Lindorm instances. We recommend that you update your IP address whitelists on a regular basis. For information about how to configure a whitelist, see Configure a whitelist.


compute engine

A compute engine is integrated into the Lindorm storage engine to provide distributed computing services based on the cloud-native architecture. The computing services can meet your computing requirements in scenarios such as data production, interactive analytics, machine learning, and graph computing. The compute engine is compatible with open source Spark standard interfaces. For more information, see Overview of the compute engine.


Java Database Connectivity (JDBC) is a Java API that specifies how a client accesses a database.

classic network

Instances in the classic network cannot be isolated by using network settings. You can block unauthorized access to the instances in the classic network only by configuring IP address whitelists.


wide table engine

The wide table engine of Lindorm is used to manage wide tables and object data. The wide table engine provides capabilities such as global secondary indexes, multi-dimensional retrieval, dynamic columns, and time to live (TTL). The wide table engine is suitable for scenarios such as the scenarios related to metadata, orders, bills, profiles, social networking, feeds, and logs. The wide table engine is compatible with standard interfaces such as SQL, HBase, Cassandra (CQL), and S3. For more information, see Overview of the wide table engine.

wide table SQL

The wide table SQL supports drivers in multiple programming languages, such as Java, Python, and Go. You can access Lindorm instances by using the drivers in multiple programming languages. For more information, see Introduction to supported SDKs in SQL-based connection to LindormTable.


Zones are physical locations that use independent power supply and networks in a region. All zones in a region provide similar services.


streaming engine

A streaming engine is an engine that is used to process streaming data. The streaming engine can store streaming data and provides lightweight computing capabilities to allow you to process streaming data. This way, you can easily store streaming data to Lindorm instances and process and apply streaming data. For more information, see Overview of the streaming engine.

logical I/O

Logical I/O indicates the read and write requests that are sent from an application to a file system.

cold storage

Cold storage refers to a storage medium that can store cold data in databases. This helps reduce storage costs. For more information, see Introduction to the cold storage feature.

Cold and hot data separation

The wide table engine of Lindorm supports cold and hot data separation. The system can automatically separate cold and hot data in tables based on user settings, and archive cold data to cold storage and hot data to hot storage. For more information, see Hot data and cold data separation.


Lindorm Tunnel Service (LTS) is a data ecosystem service that is customized based on the characteristics of Lindorm business scenarios. LTS provides easy-to-use capabilities, including data exchange, processing, and subscription. This way, you can migrate data, subscribe to real-time data, dump data to data lakes, and configure backflow to data warehouses. You can also apply multi-active redundancy based on units and implement backup and restoration. This way, LTS provides a unified data ecosystem service for Lindorm. For more information, see Introduction to LTS (formerly known as BDS).



MaxCompute, previously known as ODPS, is a fully managed data warehouse service that can process terabytes or petabytes of data at high speeds. MaxCompute provides comprehensive data import solutions and various classic distributed computing models to allow you to compute large amounts of data. DataWorks is used to import Lindorm data to MaxCompute. This way, a large scale of data can be computed. For more information, see What is MaxCompute?.


ApsaraDB for MongoDB is a stable, reliable, and scalable database service that is fully compatible with the MongoDB protocol. If various data structures exist, you can store structured data in Lindorm and unstructured data in ApsaraDB for MongoDB to meet various storage requirements. For more information, see What is ApsaraDB for MongoDB?



Object Storage Service (OSS) is a secure, cost-effective, and highly reliable service that allows you to store, back up, and archive large amounts of data in the cloud. For more information, see What is OSS?.


Open Application Programming Interface (OpenAPI) is an API that is provided by Lindorm for third-party developers .



Queries per second (QPS) refers to the number of SQL statements that are executed in a database per second, including the INSERT, SELECT, UPDATE, DELETE, and COMMIT statements.



Resource Access Management (RAM) is a service provided by Alibaba Cloud to allow you to manage user identities and resource access permissions. For more information, see What is RAM?.


ApsaraDB RDS is a stable, reliable, and scalable online database service that is built based on the Apsara Distributed File System and high-performance SSDs provided by Alibaba Cloud. ApsaraDB RDS supports the MySQL, SQL Server, PostgreSQL, and MariaDB TX database engines. ApsaraDB RDS provides a set of solutions for disaster recovery, backup, restoration, monitoring, and migration to facilitate database O&M. For more information, see What is ApsaraDB RDS?.


ApsaraDB for Redis is an in-memory database service that provides persistent storage. You can use ECS, Lindorm, and ApsaraDB for Redis together to handle a large number of read requests and reduce the response time. For more information, see What is ApsaraDB for Redis?.


time series engine

The time series engine of Lindorm is a distributed time series engine that is used for large amounts of time series data. The time series engine supports SQL queries and compression algorithms, and provides features such as large amounts of multi-dimensional time series queries and time series aggregations, downsampling, and elastic scaling. For more information, see Overview of the time series engine.

search engine

The search engine of Lindorm is used to accelerate the retrieval and analysis of multi-model data. The search engine uses core technologies such as column-oriented storage and inverted indexes to provide capabilities, such as full-text search, aggregate computing, and complex multi-dimensional queries. The search engine is suitable for scenarios such as log, bill, and profile analytics. The search engine is compatible with standard interfaces such as SQL and Apache Solr. For more information, see Overview of the search engine.

search index

The wide table engine of Lindorm supports a new index type called search index in addition to high-performance native secondary indexes. Search indexes are used in complex multi-dimensional query scenarios, including scenarios such as word segmentation, fuzzy queries, aggregate analysis, and sorting and paging. For more information, see Overview of the search index.


SSL is developed by Netscape to allow users to establish encrypted connections between web servers and browsers. SSL supports various encryption algorithms, such as RC4, MD5, and RSA. The Internet Engineering Task Force (IETF) upgraded SSL 3.0 to transport layer security (TLS).

deletion protection

The deletion protection feature can help prevent accidental releases of instances on which important services are running during operations. After the deletion protection feature is enabled for an instance, the instance cannot be released. If you want to release an instance for which deletion protection is enabled, disable deletion protection before you release the instance. For information about how to enable deletion protection, see Enable or disable deletion protection.

sequential I/O

Sequential I/O indicates the contiguous read and write operations that are performed on a disk in sequence.

random I/O

Random I/O indicates random read and write operations that are performed on a disk.



Transparent Data Encryption (TDE) is supported by Lindorm. TDE can perform real-time I/O encryption and decryption of data in data files. TDE encrypts data before the data is written to a disk, and decrypts data before the data is read from a disk and written to the memory. After TDE is enabled for your instance, the size of data files in your instance does not increase. You can use TDE without the need to modify the configurations of your application. For more information, see Enable TDE.


Transactions per second (TPS) indicates the number of transactions that are executed in the database per second.



A virtual private cloud (VPC) is an isolated network that provides higher security and higher performance than the classic network. For more information, see What is a VPC?.


file engine

The file engine is used to manage content file data and supports access to the underlying storage that is shared by the wide table engine, time series engine, and search engine. This way, the underlying data files can be imported, exported, computed, and analyzed in a more efficient manner. The file engine is compatible with the standard interfaces of the open source Hadoop Distributed File System (HDFS). For more information, see Overview of the file engine.

physical I/O

Physical I/O indicates the read and write operations that are initiated by a file system to a disk.


minor version upgrade

After Lindorm releases a new engine minor version, you can upgrade the engine of your instance to the latest minor version with a few clicks in the Lindorm console. A minor version upgrade can improve the features of the existing minor version and provide you with more new features. For more information, see Upgrade the minor engine version of a Lindorm instance.