BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage News Cloudflare Makes Basin Serverless Analytics Generally Available

Cloudflare Makes Basin Serverless Analytics Generally Available

Listen to this article -  0:00

Cloudflare has announced the general availability of Basin, a serverless analytics platform built on Apache Iceberg and R2 Object Storage. The managed service supports open data formats and integrates with tools such as DuckDB, Snowflake, and Apache Spark, with no data egress fees.

Introduced in preview as "Cloudflare Data Platform" just over a year ago, Basin combines data ingestion and SQL-based transformation, managed table maintenance, and distributed SQL queries, allowing developers to analyze large datasets without managing infrastructure. Marc Selwan, senior product manager at Cloudflare, and Micah Wylde, principal engineer at Cloudflare, explain why eliminating egress costs is central to the design:

A large driving force in the development and adoption of Basin is the continued growth we are seeing in the open Apache Iceberg ecosystem. (...) With Basin, you can read and write your data using any Iceberg-compatible engine, including PyIceberg, DuckDB, Snowflake, and Apache Spark. That kind of data portability is only possible with free egress, which allows developers to access their data in Cloudflare from the wide variety of tools in the ecosystem, regardless of region or cloud.

The platform combines three services: Basin Pipelines, formerly Cloudflare Pipelines, ingests events from Workers, HTTP endpoints, and Logpush, applies SQL transformations, and writes data to Apache Iceberg tables or R2; Basin Catalog manages Iceberg metadata and automates table maintenance; and Basin SQL provides a serverless, distributed SQL engine for querying Iceberg tables.

Basin aims to make analytics more accessible to smaller teams by running data ingestion, preparation, and queries on Cloudflare’s global network. This reduces the need to manage server clusters or move data between services, lowering the operational overhead of building and maintaining analytics pipelines. Selwan and Wylde explain the renaming:

Why Basin? A basin is where rivers from many sources come together to a single point. We felt that Basin perfectly captures how the platform is used: Pipelines brings data into Basin Catalog while Basin SQL makes it instantly queryable.

While some practitioners describe Basin as "open analytics infrastructure without the warehouse cathedral," Ramin Muradov, lead data analyst at PashaPay , comments:

I don't think it will knock Snowflake off its spot, at least not anytime soon. Cloudflare itself says Basin isn't a replacement for every warehouse workload. But there's a big layer of the market made up of teams whose data is too small to justify dedicated infrastructure and too big to fit in Excel. They now have an option.

Cloudflare is not the only cloud provider targeting unified analytics: as separately reported on InfoQ, AWS recently acquired DuckLabs and integrated DuckDB into Aurora PostgreSQL, aiming to simplify analytics across transactional and object storage data, while Google repositioned over the years BigQuery as the "single, unified AI-ready data platform."

Since its preview, Basin has increased ingestion capacity to 3 GB/s per stream, expanded SQL capabilities, improved Iceberg table maintenance, and added Logpush integration and Terraform support. Planned features, with no committed release dates, include real-time processing capabilities, support for the latest Iceberg specification, adaptive table-maintenance, and additional controls for data sovereignty and access management.

Cloudflare's Basin tutorial explains how to ingest events with Basin Pipelines, store them in Iceberg tables managed by Basin Catalog, and query them using Basin SQL.

About the Author

Rate this Article

Adoption
Style

BT