Skip to main content
SQL Workspaces provide a managed architecture for processing streams from StreamNative Pulsar and Kafka clusters with PostgreSQL-compatible SQL.
SQL Workspaces are available by invitation only. During Private Preview, manage SQLWorkspace and SQLCatalog resources through the StreamNative Cloud Console. You can query a workspace through SQL Studio or its native PostgreSQL endpoint.

Get started

Create a workspace, add a catalog, and run a query.

Understand access control

Learn how cloud resource and SQLWorkspace engine permissions work.

Understand SQLWorkspace

Learn about the engine model, placement, lifecycle, and query endpoints.

Understand SQLCatalog

Learn how Pulsar and Kafka clusters map to databases and topic sources.

Architecture

Components

Control flow

  1. A user creates a SQLWorkspace in an eligible hosted location or ready BYOC Cloud Environment through the Cloud Console.
  2. StreamNative provisions the selected SQLWorkspace engine and its managed metadata and object storage. During Private Preview, the engine is RisingWave and SQLWorkspace engine infrastructure is supported only on AWS.
  3. The user adds a Pulsar or Kafka cluster as a SQLCatalog.
  4. StreamNative creates a database for the catalog and periodically discovers eligible topics to create missing source objects.
  5. The user creates tables or materialized views based on the managed topic sources for subsequent processing.

Query flow

  1. Pulsar or Kafka delivers new events to the connected topics.
  2. The topic sources make those events available to the SQLWorkspace engine.
  3. The SQLWorkspace engine evaluates ad hoc queries or continuously maintains materialized views.
  4. Users submit SQL and retrieve results through SQL Studio or a PostgreSQL-compatible client.