You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-6Lines changed: 5 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@
39
39
</a>
40
40
</div>
41
41
42
-
RisingWave is the world's most advanced streaming database engineered to provide the <i><b>simplest</b></i> and <i><b>most cost-efficient</b></i> approach for <b>processing</b>, <b>analyzing</b>, and <b>managing</b> real-time event streaming data. It provides both a Postgres-compatible [SQL interface](https://docs.risingwave.com/sql/overview) and a DataFrame-style [Python interface](https://docs.risingwave.com/python-sdk/intro).
42
+
RisingWave is the world's most advanced event stream processing platform engineered to provide the <i><b>simplest</b></i> and <i><b>most cost-efficient</b></i> approach for <b>processing</b>, <b>analyzing</b>, and <b>managing</b> real-time event streaming data. It provides both a Postgres-compatible [SQL interface](https://docs.risingwave.com/sql/overview) and a DataFrame-style [Python interface](https://docs.risingwave.com/python-sdk/intro).
43
43
44
44
RisingWave can <b>ingest</b> millions of events per second, continuously <b>join and analyze</b> live data streams with historical tables, <b>serve</b> ad-hoc queries at low latency, and <b>deliver</b> fresh, consistent results wherever needed.
45
45
@@ -57,11 +57,10 @@ To learn about other installation options, such as using a Docker image, see [Qu
57
57
## When is RisingWave the perfect fit?
58
58
RisingWave is the ideal solution for:
59
59
60
-
* Managing real-time data sources like Kafka streams, database CDC, and more.
61
-
* Executing complex, on-the-fly queries, including joins, aggregations, and time windowing.
62
-
* Interactively and concurrently exploring consistent, up-to-the-moment results.
63
-
* Seamlessly delivering results to downstream systems.
64
-
* Processing both streaming and batch data with a unified codebase.
60
+
***Ingestion**: Ingest millions of events per second from both streaming and batch data sources.
61
+
***Stream processing**: Perform real-time incremental data processing to join and analyze live data streams with historical tables.
62
+
***Serving**: Persist data and serve ad-hoc queries with single-digit millisecond latency.
63
+
***Delivery**: Deliver fresh, consistent results to data lakes (e.g., Apache Iceberg) or any destination.
0 commit comments