Integrations
Integrations is where you wire VeloDB Cloud up to data sources, lakehouses, and other systems. The pages in this section correspond to the Work with data group in the left navigation:
| Page | What it covers |
|---|---|
| Catalogs | Browse the internal catalog and connect external catalogs (Hive, Iceberg, Hudi, object storage, etc.) without copying data into VeloDB. |
| Import | Continuously ingest or batch-load data from databases (MySQL, PostgreSQL), object storage (S3), and event streams (Kafka, Confluent, Amazon MSK). |
| Migration | One-stop full-data migration from Apache Doris, VeloDB, or StarRocks into a VeloDB Cloud warehouse. |
Choosing an integration
A short rule of thumb:
- Use a catalog when you want to query data in place — the data stays where it lives and VeloDB queries it on demand. External catalogs are the right choice for lakehouse formats and object-storage data you do not want to copy.
- Use Import when you want a managed pipeline — VeloDB ingests the data into the warehouse on a schedule or in real time, with automatic table creation, CDC support for databases, and offset tracking for event streams.
- Use Migration when you are one-shot moving an entire warehouse from another system (Doris / VeloDB / StarRocks). It runs once, uses a temporary object-storage staging area, and cleans itself up.