

RisingWave adopts a decoupled compute and storage architecture, allowing you to scale compute and storage independently. This ensures better performance at a lower cost as your data volume grows.
| KsqlDB | RisingWave | |
|---|---|---|
| SQL Compatibility | Basic SQL, limited features | PostgreSQL-compatible SQL with advanced features for complex queries |
| Separation of Compute/Storage | Compute and storage tied to Kafka | Decoupled architecture for independent compute and storage scaling |
| State Backend | RocksDB via Kafka | Native tiered storage for optimized performance and scalability |
| Data Consistency | At-least-once and exactly-once via Kafka Streams | Supports exactly-once semantics, out-of-order processing, and snapshot reads |
| Fault Tolerance | Relies on Kafka, no checkpointing | Checkpointing and consistent snapshots for fast recovery |
| High Availability | Supported | Supported, with more flexible recovery mechanisms |
| SQL Compatibility | PostgreSQL-compatible SQL with advanced features for complex queries |
| Separation of Compute/Storage | Decoupled architecture for independent compute and storage scaling |
| State Backend | Native tiered storage for optimized performance and scalability |
| Data Consistency | Supports exactly-once semantics, out-of-order processing, and snapshot reads |
| Fault Tolerance | Checkpointing and consistent snapshots for fast recovery |
| High Availability | Supported, with more flexible recovery mechanisms |
