SQIP concepts

SQIP is the control plane for a shared event-streaming platform. You use its web console to create resources, connect systems, assign access, and understand operational health.

Control plane and data plane

SQIP presents two related parts as one service:

You do not need to manage the data-plane infrastructure yourself. SQIP turns your console choices into managed resources and shows their progress and health.

The customer journey

Tenant
  └── Shared cluster association
        └── Namespace
              ├── Topic
              │     └── Optional schema
              ├── API keys
              └── Connectors

1. A tenant is your organization's isolated boundary.
2. A cluster association connects that tenant to SQIP's managed shared capacity.
3. A namespace groups related topics and defines a storage quota.
4. A topic is the named stream that applications and connectors use.
5. A schema defines the shape of topic records.
6. An API key allows an application to produce, consume, or do both within one namespace.
7. A connector moves records between a topic and an external system.

Sources and sinks

• A source connector reads from an external system and writes to a SQIP topic.
• A sink connector reads from a SQIP topic and writes to an external system.

For example:

Orders API → HTTP source → orders.raw topic
orders.ready topic → PostgreSQL sink → reporting database

Managed and asynchronous changes

Some SQIP actions finish immediately, while others are queued and completed in the background. Cluster and connector screens show the current status so you can safely leave the page and return later.

Common status meanings include: