All Products
Search
Document Center

Lindorm:Introduction

Last Updated:Jul 01, 2026

Lindorm Search Engine is a managed search service for large-scale data workloads. It provides efficient index read/write capabilities, low-cost data storage, and rapid elastic scaling. It is ideal for use cases like site search, order queries, log analytics, and application performance monitoring (APM).

Core capabilities

  • Low cost

    The service supports multiple high-efficiency compression algorithms to reduce index storage costs. It also uses hot-and-cold data tiering to offload historical data to lower-cost storage media.

  • Cloud-native elasticity

    Built on a cloud-native storage-compute disaggregation architecture, the service can rapidly scale replicas to efficiently handle traffic peaks.

  • High availability

    A distributed, high-availability design eliminates any single point of failure in the cluster. The service also intelligently identifies abnormal traffic and applies fast isolation and degradation to ensure system stability.

  • Rich ecosystem

    Data can be accessed using standard SQL statements. No proprietary query language is required.

Use cases

  • Multi-field queries

    Store large volumes of tracking records and retrieve order details by querying across multiple fields simultaneously. This is ideal for logistics and order management workloads.

  • Geolocation search

    Store vehicle passage records and retrieve specific entries by combining conditions such as license plate numbers and geographic coordinates. This is suitable for traffic monitoring and location-aware applications.

  • Text search

    Store large volumes of text and retrieve results that match a specific phrase. This is useful for product catalogs and content platforms where users need to find specific products or documents.

Service activation

To activate Lindorm Search Engine, see the Activation guide.

Get started

You can use standard SQL statements and web-based operations to interact with Lindorm Search Engine. For more information, see Manage index tables.