Kind
streaming
Vendor
RisingWave Labs
Workload
Streaming SQL and real-time materialized views
Storage backend
Object storage (S3) for state and tables
Separates storage and compute
Yes
Object storage is source of truth
Yes
Open source
Yes
Access paths
Open source, RisingWave Cloud
RisingWave is a streaming database. It ingests events, maintains incrementally updated materialized views, and answers queries over live data using the Postgres wire protocol. It belongs here because of where it keeps its state. Tables, materialized views, and internal operator state are persisted to object storage rather than to local disk.
Why it qualifies
- Object storage for state. RisingWave stores its state and tables in object storage (S3), which the RisingWave team says is far cheaper than holding that state in memory.
- Storage and compute are separate. Compute nodes can be scaled independently because the durable state lives in object storage.
- Operational workload. It powers real-time features and dashboards with sub-second freshness, which is operational rather than batch analytical.
Where it sits in the category
RisingWave sits near the edge of the category. Its programming model is streaming and incremental computation rather than request-response transactions, so it is not a drop-in replacement for a relational lakebase. It is included because it shows the same architectural idea, separation of storage and compute with object storage as the durable layer, applied to a different shape of workload.