Skip to content

Commit bb3be10

Browse files
yingjunwuhengm3467ShanlanLi
authored
chore: Update README.md (#14808)
Co-authored-by: hengm3467 <[email protected]> Co-authored-by: Shanlan(Lily) <[email protected]>
1 parent dad4387 commit bb3be10

File tree

1 file changed

+12
-27
lines changed

1 file changed

+12
-27
lines changed

README.md

Lines changed: 12 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@
99

1010
<div align="center">
1111

12-
### 🌊Stream Processing Redefined.
12+
### 🌊Reimagine Stream Processing.
1313

1414
</div>
1515

@@ -60,39 +60,27 @@
6060
</a>
6161
</div>
6262
63-
RisingWave is a distributed SQL streaming database engineered to provide the <i><b>simplest</b></i> and <i><b>most cost-efficient</b></i> approach for <b>processing</b> and <b>managing</b> streaming data with utmost reliability.
63+
RisingWave is a distributed SQL 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.
6464

6565

6666
![RisingWave](https://github.com/risingwavelabs/risingwave-docs/blob/main/docs/images/new_archi_grey.png)
6767

6868
## Try it out in 5 minutes
69-
**Docker**
69+
Docker pull:
7070
```
7171
docker run -it --pull=always -p 4566:4566 -p 5691:5691 risingwavelabs/risingwave:latest playground
7272
```
73-
**Mac**
74-
```
75-
brew tap risingwavelabs/risingwave
76-
brew install risingwave
77-
risingwave playground
78-
```
79-
**Ubuntu**
80-
```
81-
wget https://github.com/risingwavelabs/risingwave/releases/download/v1.5.0/risingwave-v1.5.0-x86_64-unknown-linux-all-in-one.tar.gz
82-
tar xvf risingwave-v1.5.0-x86_64-unknown-linux-all-in-one.tar.gz
83-
./risingwave playground
84-
```
8573
Now connect to RisingWave using `psql`:
8674
```
8775
psql -h localhost -p 4566 -d dev -U root
8876
```
89-
Learn more at [Quick Start](https://docs.risingwave.com/docs/current/get-started/).
77+
Don’t have Docker? Learn how to install RisingWave on Mac, Ubuntu, and other environments at [Quick Start](https://docs.risingwave.com/docs/current/get-started/).
9078

9179
## Production deployments
9280

93-
For **single-node Docker deployments**, please refer to [Docker Compose](https://docs.risingwave.com/docs/current/risingwave-trial/?method=docker-compose).
81+
For **single-node deployment**, please refer to [Docker Compose](https://docs.risingwave.com/docs/current/risingwave-trial/?method=docker-compose).
9482

95-
For **Kubernetes deployments**, please refer to [Kubernetes with Helm](https://docs.risingwave.com/docs/current/risingwave-k8s-helm/) or [Kubernetes with Operator](https://docs.risingwave.com/docs/current/risingwave-kubernetes/).
83+
For **distributed deployment**, please refer to [Kubernetes with Helm](https://docs.risingwave.com/docs/current/risingwave-k8s-helm/) or [Kubernetes with Operator](https://docs.risingwave.com/docs/current/risingwave-kubernetes/).
9684

9785
**RisingWave Cloud** the easiest way to run a fully-fledged RisingWave cluster. Try it out for free at: [cloud.risingwave.com](https://cloud.risingwave.com).
9886

@@ -135,17 +123,14 @@ RisingWave is fundamentally a database that **extends beyond basic streaming dat
135123
* Schema change
136124
* Processing of semi-structured data
137125

126+
## In-production use cases
127+
Within your data stack, RisingWave can assist with:
138128

139-
## RisingWave's limitations
140-
RisingWave isn’t a panacea for all data engineering hurdles. It has its own set of limitations:
141-
* **No programmable interfaces**
142-
* RisingWave does not provide low-level APIs in languages like Java and Scala, and does not allow users to manage internal states manually (unless you want to hack!). _For coding in Java, Python, and other languages, please consider using RisingWave's [User-Defined Functions (UDF)](https://docs.risingwave.com/docs/current/user-defined-functions/)_.
143-
* **No support for transaction processing**
144-
* RisingWave isn’t cut out for transactional workloads, thus it’s not a viable substitute for operational databases dedicated to transaction processing. _However, it supports [read-only transactions](https://docs.risingwave.com/docs/current/transactions/#read-only-transactions), ensuring data freshness and consistency. It also comprehends the transactional semantics of upstream database [Change Data Capture (CDC)](https://docs.risingwave.com/docs/current/transactions/#transactions-within-a-cdc-table)_.
145-
129+
* Processing and transforming event streaming data in real time
130+
* Offloading event-driven queries (e.g., materialized views, triggers) from operational databases
131+
* Performing real-time ETL (Extract, Transform, Load)
146132

147-
## In-production use cases
148-
Like other stream processing systems, the primary use cases of RisingWave include monitoring, alerting, real-time dashboard reporting, streaming ETL (Extract, Transform, Load), machine learning feature engineering, and more. It has already been adopted in fields such as financial trading, manufacturing, new media, logistics, gaming, and more. Check out [customer stories](https://www.risingwave.com/use-cases/).
133+
RisingWave is extensively utilized in real-time applications such as monitoring, alerting, dashboard reporting, ML feature engineering, among others. It has already been adopted in fields such as financial trading, manufacturing, new media, logistics, gaming, and more. Check out [customer stories](https://www.risingwave.com/use-cases/).
149134

150135
## Community
151136

0 commit comments

Comments
 (0)