risingwave
flink-statefun
risingwave | flink-statefun | |
---|---|---|
27 | 18 | |
6,309 | 493 | |
2.2% | 1.0% | |
10.0 | 5.1 | |
4 days ago | 5 months ago | |
Rust | Java | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
risingwave
-
Proton, a fast and lightweight alternative to Apache Flink
How does this compare to RisingWave and Materialize?
https://github.com/risingwavelabs/risingwave
-
RisingWave's Roadmap - Redefining Stream Processing with the Rust-Built Streaming Database
Hey everyone - One and a half year ago, we open sourced RisingWave, a Rust-built streaming database, under Apache 2.0 license. Two weeks ago, we released RisingWave 1.3. Just last week, we unveiled RisingWave's roadmap.
- Risingwave: Redefining Stream Processing
-
Highlights of RisingWave v1.3: The Open-Source Streaming Database
Look out for next month’s edition to see what new, exciting features will be added. Check out the RisingWave GitHub repository to stay up to date on the newest features and planned releases.
- Optimizing Rust Code for the Lsm-Tree Iterator in RisingWave
- Hummock: A Storage Engine Designed for Stream Processing
-
RisingWave 1.2 released - the open-source streaming database built in Rust
If interested, please feel free to join our Slack community! Thanks eveyone for your generous support!
-
Query materialized views with Java, Spring, and streaming database
We will spin up on our local environment the existing RisingWave fully-featured demo cluster on GitHub which is composed of multiple RisingWave components. To simplify this task, it leverages docker-compose.yaml file which includes additional containers for Kafka message broker, and data generation service.
-
Real-time Data Processing Pipeline With MongoDB, Kafka, Debezium And RisingWave
To complete the steps in this guide, you must download/clone and work on an existing sample project on GitHub. The project uses Docker for convenience and consistency. It provides a containerized development environment that includes the services you need to build the sample data pipeline.
-
Flink CDC / alternatives
Hey have you looked at RisingWave (https://github.com/risingwavelabs/risingwave) before? It's a stream processing system with PostgreSQL interface. It also have integrations similar to Flink CDC.
flink-statefun
-
flink-statefun VS quix-streams - a user suggested alternative
2 projects | 7 Dec 2023
-
Snowflake - what are the streaming capabilities it provides?
When low latency matters you should always consider an ETL approach rather than ELT, e.g. collect data in Kafka and process using Kafka Streams/Flink in Java or Quix Streams/Bytewax in Python, then sink it to Snowflake where you can handle non-critical workloads (as is the case for 99% of BI/analytics). This way you can choose the right path for your data depending on how quickly it needs to be served.
-
JR, quality Random Data from the Command line, part I
Sometimes we may need to generate random data of type 2 in different streams, so the "coherency" must also spread across different entities, think for example to referential integrity in databases. If I am generating users, products and orders to three different Kafka topics and I want to create a streaming application with Apache Flink, I definitely need data to be coherent across topics.
-
Brand Lift Studies on Reddit
The Treatment and Control audiences need to be stored for future low-latency, high-reliability retrieval. Retrieval happens when we are delivering the survey, and informs the system which users to send surveys to. How is this achieved at Reddit’s scale? Users interact with ads, which generate events that are sent to our downstream systems for processing. At the output, these interactions are stored in DynamoDB as engagement records for easy access. Records are indexed on user ID and ad campaign ID to allow for efficient retrieval. The use of stream processing (Apache Flink) ensures this whole process happens within minutes, and keeps audiences up to date in real-time. The following high-level diagram summarizes the process:
-
Query Real Time Data in Kafka Using SQL
Most streaming database technologies use SQL for these reasons: RisingWave, Materialize, KsqlDB, Apache Flink, and so on offering SQL interfaces. This post explains how to choose the right streaming database.
-
How to choose the right streaming database
Apache Flink.
-
5 Best Practices For Data Integration To Boost ROI And Efficiency
There are different ways to implement parallel dataflows, such as using parallel data processing frameworks like Apache Hadoop, Apache Spark, and Apache Flink, or using cloud-based services like Amazon EMR and Google Cloud Dataflow. It is also possible to use parallel dataflow frameworks to handle big data and distributed computing, like Apache Nifi and Apache Kafka.
-
Forward Compatible Enum Values in API with Java Jackson
We’re not discussing the technical details behind the deduplication process. It could be Apache Flink, Apache Spark, or Kafka Streams. Anyway, it’s out of the scope of this article.
-
Which MQTT (or similar protocol) broker for a few 10k IoT devices with quite a lot of traffic?
One can also consider https://flink.apache.org/ instead of Kafka for connecting a large number of devices.
-
Apache Pulsar vs Apache Kafka - How to choose a data streaming platform
Both Kafka and Pulsar provide some kind of stream processing capability, but Kafka is much further along in that regard. Pulsar stream processing relies on the Pulsar Functions interface which is only suited for simple callbacks. On the other hand, Kafka Streams and ksqlDB are more complete solutions that could be considered replacements for Apache Spark or Apache Flink, state-of-the-art stream-processing frameworks. You could use them to build streaming applications with stateful information, sliding windows, etc.
What are some alternatives?
materialize - The data warehouse for operational workloads.
opensky-api - Python and Java bindings for the OpenSky Network REST API
datafuse - An elastic and reliable Cloud Warehouse, offers Blazing Fast Query and combines Elasticity, Simplicity, Low cost of the Cloud, built to make the Data Cloud easy [Moved to: https://github.com/datafuselabs/databend]
Apache Spark - Apache Spark - A unified analytics engine for large-scale data processing
ksql - The database purpose-built for stream processing applications.
debezium - Change data capture for a variety of databases. Please log issues at https://issues.redhat.com/browse/DBZ.
greptimedb - An open-source, cloud-native, distributed time-series database with PromQL/SQL/Python supported. Available on GreptimeCloud.
redpanda - Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM!
chdb - chDB is an embedded OLAP SQL Engine 🚀 powered by ClickHouse
Apache Pulsar - Apache Pulsar - distributed pub-sub messaging system
roapi - Create full-fledged APIs for slowly moving datasets without writing a single line of code.
faust - Python Stream Processing. A Faust fork