# risingwave **Repository Path**: mrlijing/risingwave ## Basic Information - **Project Name**: risingwave - **Description**: No description available - **Primary Language**: Unknown - **License**: Apache-2.0 - **Default Branch**: main - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2025-02-11 - **Last Updated**: 2025-02-11 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README

### 🌊 Ride the Wave of Real-Time Data.

Docs | Benchmarks | Demos

Slack X YouTube
RisingWave is the world's most advanced event stream processing platform engineered to provide the simplest and most cost-efficient approach for processing, analyzing, and managing 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). RisingWave can ingest millions of events per second, continuously join and analyze live data streams with historical tables, serve ad-hoc queries at low latency, and deliver fresh, consistent results wherever needed. ![RisingWave](./docs/dev/src/images/architecture_20250127.png) ## Try it out in 60 seconds Install RisingWave standalone mode: ```shell curl -L https://risingwave.com/sh | sh ``` To learn about other installation options, such as using a Docker image, see [Quick Start](https://docs.risingwave.com/docs/current/get-started/). ## What is RisingWave optimized for? RisingWave simplifies the development of real-time data pipelines and applications. It is purpose-built to: * **Ingestion**: Ingest millions of events per second from both streaming and batch data sources. * **Stream processing**: Perform real-time incremental data processing to join and analyze live data streams with historical tables. * **Serving**: Persist data and serve ad-hoc queries with single-digit millisecond latency. * **Delivery**: Deliver fresh, consistent results to data lakes (e.g., Apache Iceberg) or any destination. ## Why is RisingWave special? RisingWave stands apart from traditional stream processing systems due to its: ### PostgreSQL compatibility Connect via the PostgreSQL wire protocol - using psql, JDBC, or any Postgres tool. * **Seamless integration**: Works with a wide range of tools in the PostgreSQL ecosystem. * **Expressive SQL**: Supports structured, semi-structured, and unstructured data using a rich, familiar SQL dialect. * **No manual state tuning**: Eliminates the need for complex state management configurations. ### Zero disk architecture All data lives in S3 (or equivalent), with local disk used only as a cache. * **Optimized for complex queries**: Ensures high performance for stateful operations like joins and time windowing. * **Fast failure recovery**: Recovers from system crashes within seconds. * **Dynamic scaling**: Adjusts resources instantly to handle workload spikes. ## In what use cases does RisingWave excel? RisingWave is particularly effective for the following use cases: * **Streaming analytics**: Achieve sub-second data freshness in live dashboards, ideal for high-stakes scenarios like stock trading, sports betting, and IoT monitoring. * **Event-driven applications**: Develop sophisticated monitoring and alerting systems for critical applications such as fraud and anomaly detection. * **Real-time data enrichment**: Continuously ingest data from diverse sources, conduct real-time data enrichment, and efficiently deliver the results to downstream systems. * **Feature engineering**: Transform batch and streaming data into features in your machine learning models using a unified codebase, ensuring seamless integration and consistency. ## Production deployments [**RisingWave Cloud**](https://cloud.risingwave.com) offers the easiest way to run RisingWave in production. For **Docker deployment**, please refer to [Docker Compose](https://docs.risingwave.com/docs/current/risingwave-docker-compose/). For **Kubernetes 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/). ## Community Looking for help, discussions, collaboration opportunities, or a casual afternoon chat with our fellow engineers and community members? Join our [Slack workspace](https://risingwave.com/slack)! ## Notes on telemetry RisingWave uses [Scarf](https://scarf.sh/) to collect anonymized installation analytics. These analytics help support us understand and improve the distribution of our package. The privacy policy of Scarf is available at [https://about.scarf.sh/privacy-policy](https://about.scarf.sh/privacy-policy). RisingWave also collects anonymous usage statistics to better understand how the community is using RisingWave. The sole intention of this exercise is to help improve the product. Users may opt out easily at any time. Please refer to the [user documentation](https://docs.risingwave.com/docs/current/telemetry/) for more details. ## License RisingWave is distributed under the Apache License (Version 2.0). Please refer to [LICENSE](LICENSE) for more information. ## Contributing Thanks for your interest in contributing to the project! Please refer to [RisingWave Developer Guide](https://risingwavelabs.github.io/risingwave/) for more information.