All Products
Search
Document Center

Realtime Compute for Apache Flink:Paimon Streaming Lakehouse Architecture Solution Selection

Last Updated:Aug 13, 2026

Apache Paimon is a lakehouse storage format that unifies streaming and batch data processing. Built on log-structured merge-tree (LSM) technology, Paimon delivers real-time update semantics at the lake layer with consistent reads and high throughput. You can use Paimon tables in Realtime Compute for Apache Flink to build a streaming lakehouse on cloud storage such as Object Storage Service (OSS).

Paimon integrates with Apache Flink for stream processing and Apache Spark for batch processing through a single storage format. Key capabilities:

  • Real-time data ingestion: Ingest tens of millions of records from database change streams such as MySQL CDC, with automatic schema change synchronization and low latency.

  • Unified stream and batch processing: Read the same Paimon table as a bounded batch source in Spark or as an unbounded changelog stream in Flink, with no format conversion required.

  • Broad ecosystem integration: Connect Paimon tables to Realtime Compute for Apache Flink, E-MapReduce (Spark, StarRocks, Hive, and Trino), and MaxCompute without data duplication.

  • Low-latency OLAP queries: Deletion vectors and primary key indexes keep query latency at the minute level for streaming, batch, and online analytical processing (OLAP) workloads.

For the full specification, see Apache Paimon.

Usage

Get started with Paimon

Create a Paimon catalog

A Paimon catalog is a centralized registry for Paimon tables stored in external systems such as OSS. Other Alibaba Cloud services access tables through the same catalog. You can set up a catalog in any of the following ways:

Create a Paimon table

Write data to a Paimon table

Consume data from a Paimon table

  • Query or consume data from a Paimon table in batch or streaming mode. For more information, see Consume data from a Paimon table. To consume data from a primary key table in streaming mode, configure the changelog producer first.

  • Configure the consumer offset of a Paimon table. For more information, see Consume data from a specified offset.

  • Save the consumer offset of a Paimon table or retain expired snapshot files that are still referenced by active consumers. For more information, see Specify a consumer ID.

  • Run a batch job to read the historical state of a Paimon table from a specific snapshot. For more information, see Batch time travel.

Maintain a Paimon table