noisepage
risingwave
noisepage | risingwave | |
---|---|---|
4 | 27 | |
1,677 | 6,331 | |
- | 2.5% | |
0.0 | 10.0 | |
over 1 year ago | 1 day ago | |
C++ | Rust | |
MIT License | 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.
noisepage
-
The Part of PostgreSQL We Hate the Most (Multi-Version Concurrency Control)
> Carne
Okay, so, noisepage appears to be open source https://github.com/cmu-db/noisepage/
But I can't find the Ottertune Github page
Is any part of Ottertune open source?
-
Rethinking Stream Processing and Streaming Databases
I was one of the main authors of a research project called Peloton (https://github.com/cmu-db/peloton) which was later rebranded to NoisePage (https://github.com/cmu-db/noisepage). The initial version of RisingWave actually borrowed a lot from Peloton (fun fact: that's also how DuckDB https://duckdb.org/ started!), but we decided to rewrite in Rust due to development cost and security (e.g., memory leakage) considerations (more info: https://www.risingwave-labs.com/blog/building-a-cloud-database-from-scratch-why-we-moved-from-cpp-to-rust/).
-
Show HN: OtterTune โ Automated Database Tuning Service for RDS MySQL/Postgres
> If I may, can you please shed light on why Peloton had to be archived and in essence re-done with OtterTune. Interested in your team's learnings from it from a software engineering point of view.
Peloton and OtterTune are completely different projects. Peloton was abandoned and rewritten as NoisePage (https://noise.page). OtterTune has always been OtterTune.
See this recent interview where I discuss why we gave up on Peloton:
https://www.ibm.com/cloud/blog/database-deep-dives-with-andy...
> - How did the team ensure this project doesn't suffer from the same disadvantages as its predecessor?
Again, different projects. OtterTune is all about not having to modify the internals of Postgres, MySQL, and any other DBMS. This is why we were able to support Oracle in the academic version in a short amount of time:
https://ottertune.com/blog/vldb-autonomous-database-tuning-i...
> - What would you advise other teams undertaking a rewrite to pay off their tech debts?
It is hard for to provide general advice for this question because every situation is different.
> How does this project compare to / contrast with Google's and SingleStore's efforts in this space?
I am not familiar with Google or SingleStore using ML in the manner that we are with OtterTune to tune configuration knobs. Or at least I have not seen anything public about it.
These days Oracle is the most aggressive with pushing automated tuning capabilities (Oracle's autonomous DBaaS, AutoPilot for MySQL Heatwave). The difference with these approaches and OtterTune is that right now we are focused on configuration tuning (to avoid data privacy issues) and our core approach is platform/DBMS agnostic.
> Any chance we see you do a Peter Bailis and Sisu Data this? (:
I don't know what you mean by this? Peter Bailis is the Ryan Gosling of databases.
-
Resumable Allocator?
The state of the art for this sort of thing is (Leanstore/Umbra - https://umbra-db.com/) or the new NoisePage database (https://github.com/cmu-db/noisepage/tree/master/src/storage). There is also the HyRise database, but that one focuses more on datasets that fit entirely in memory (https://hpi.de/plattner/projects/hyrise.html)
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.