From bb3be1091bc00311428dde002f9898355f6f9926 Mon Sep 17 00:00:00 2001 From: Yingjun Wu Date: Fri, 26 Jan 2024 03:06:00 -0800 Subject: [PATCH] chore: Update README.md (#14808) Co-authored-by: hengm3467 <100685635+hengm3467@users.noreply.github.com> Co-authored-by: Shanlan(Lily) <150168166+ShanlanLi@users.noreply.github.com> --- README.md | 39 ++++++++++++--------------------------- 1 file changed, 12 insertions(+), 27 deletions(-) diff --git a/README.md b/README.md index 11793ce064647..753e1d598c60e 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@
-### 🌊Stream Processing Redefined. +### 🌊Reimagine Stream Processing.
@@ -60,39 +60,27 @@ -RisingWave is a distributed SQL streaming database engineered to provide the simplest and most cost-efficient approach for processing and managing streaming data with utmost reliability. +RisingWave is a distributed SQL streaming database engineered to provide the simplest and most cost-efficient approach for processing, analyzing, and managing real-time event streaming data. ![RisingWave](https://github.com/risingwavelabs/risingwave-docs/blob/main/docs/images/new_archi_grey.png) ## Try it out in 5 minutes -**Docker** +Docker pull: ``` docker run -it --pull=always -p 4566:4566 -p 5691:5691 risingwavelabs/risingwave:latest playground ``` -**Mac** -``` -brew tap risingwavelabs/risingwave -brew install risingwave -risingwave playground -``` -**Ubuntu** -``` -wget https://github.com/risingwavelabs/risingwave/releases/download/v1.5.0/risingwave-v1.5.0-x86_64-unknown-linux-all-in-one.tar.gz -tar xvf risingwave-v1.5.0-x86_64-unknown-linux-all-in-one.tar.gz -./risingwave playground -``` Now connect to RisingWave using `psql`: ``` psql -h localhost -p 4566 -d dev -U root ``` -Learn more at [Quick Start](https://docs.risingwave.com/docs/current/get-started/). +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/). ## Production deployments -For **single-node Docker deployments**, please refer to [Docker Compose](https://docs.risingwave.com/docs/current/risingwave-trial/?method=docker-compose). +For **single-node deployment**, please refer to [Docker Compose](https://docs.risingwave.com/docs/current/risingwave-trial/?method=docker-compose). -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/). +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/). **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). @@ -135,17 +123,14 @@ RisingWave is fundamentally a database that **extends beyond basic streaming dat * Schema change * Processing of semi-structured data +## In-production use cases +Within your data stack, RisingWave can assist with: -## RisingWave's limitations -RisingWave isn’t a panacea for all data engineering hurdles. It has its own set of limitations: -* **No programmable interfaces** - * 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/)_. -* **No support for transaction processing** - * 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)_. - +* Processing and transforming event streaming data in real time +* Offloading event-driven queries (e.g., materialized views, triggers) from operational databases +* Performing real-time ETL (Extract, Transform, Load) -## In-production use cases -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/). +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/). ## Community