I've been running this in prod self hosted for around 6 months (podman with docker compose, minio for s3, streaming with pulsar). We have built position calculations for risk monitoring and booking enrichment pipelines. Risingwave is a much better alternative to Kafka Streams: primarily around consistency, sql first, easy state query and deployment.
The RisingWave team are pretty responsive on slack and the ask ai feature also helps to solve questions. They have coverage from Singapore, China and California.
Issues we have seen have mostly been related to reliability of our on prem Minio cluster which is used to store the data. Other bugs do appear from release to release but once raised get attention quickly.
This seems very good. Always wondering what are the usecases for this apart for observability/real-time analytics? Do people use this for incremental view maintenance in Postgres?
This and Materialize seemed like great tools. I met some of the team of Rising Wave at the Kafka conference last year in London and was impressed by their work. It may be great if you need such a tool.
In the end, I went with ClickHouse and it's materialized views feature. It might not be quite as powerful as what these other tools are doing, but it works for us, and it's really easy to set up. Before we were using Timescale's continuous aggregates, which had good performance, but require some domain knowledge to setup. ClickHouse materialized views are great because you don't need to be an expert to use them. And even so, performance is still very good.
My use-case is IoT devices sending data, and I'd want to keep the eg last 6 months of data for review, and some agregates, and archive + delete older data
I was going to go with Timescaledb for "simplicity" (eg having a single database)
I apologize for this stupid question but whenever i see products like this or kafka, i cant help but wonder. when exactly do you need a system like this compared to a traditional redis pub sub?
10 comments
[ 3.8 ms ] story [ 48.0 ms ] threadThe RisingWave team are pretty responsive on slack and the ask ai feature also helps to solve questions. They have coverage from Singapore, China and California.
Issues we have seen have mostly been related to reliability of our on prem Minio cluster which is used to store the data. Other bugs do appear from release to release but once raised get attention quickly.
In the end, I went with ClickHouse and it's materialized views feature. It might not be quite as powerful as what these other tools are doing, but it works for us, and it's really easy to set up. Before we were using Timescale's continuous aggregates, which had good performance, but require some domain knowledge to setup. ClickHouse materialized views are great because you don't need to be an expert to use them. And even so, performance is still very good.
We wrote about it briefly here: https://blog.picnic.nl/building-a-real-time-analytics-platfo...
I was going to go with Timescaledb for "simplicity" (eg having a single database)
would Postgres+Clickhouse be indicated for this?