PolyScale and ClickHouse Materialized Views(polyscale.ai)
polyscale.ai
PolyScale and ClickHouse Materialized Views
https://www.polyscale.ai/blog/polyscale-metrics-materialized-views/
13 comments
RisingWave is another option worth considering. Open source and cloud-native from the get-go: https://www.risingwave.dev/docs/latest/intro/
ClickHouse has a couple of features along this line: live views and window views. Here's a blog that compares them.
https://altinity.com/blog/battle-of-the-views-clickhouse-win...
Disclaimer: I work for Altinity. Polyscale is a customer.
https://altinity.com/blog/battle-of-the-views-clickhouse-win...
Disclaimer: I work for Altinity. Polyscale is a customer.
I did a deep dive video on some of the options around Clickhouse materialised views too:
https://m.youtube.com/watch?v=i7VYsf1e2qU
https://m.youtube.com/watch?v=i7VYsf1e2qU
Related to this and Polyscale use case. Would this work ?
CREATE WINDOW VIEW IF NOT EXISTS minute_metrics_wv minute_metrics_tt AS SELECT ... FROM raw_metrics WHERE ... GROUP BY ...
RethinkDB (RIP) was really big on this concept and we used it for a few applications back in the day. Even since then (~2016) it doesn't seem to have caught on to any other major DBs.
Check materialize[1]
[1] https://materialize.com/
[1] https://materialize.com/
Materialize looks like a perfect tool for the job should the need ever arise.
I think my ideal would be for the functionality to be baked directly into PostgreSQL.
Has anyone here used it?
Any comments on speed/scalability/reliability?
The self hosted license seems fairly permissive (Don't cluster, don't let your users manage the database views/queries [IANAL, read the license yourself]), but I'm hesitant given that I have never heard anyones stories about production use.
I think my ideal would be for the functionality to be baked directly into PostgreSQL.
Has anyone here used it?
Any comments on speed/scalability/reliability?
The self hosted license seems fairly permissive (Don't cluster, don't let your users manage the database views/queries [IANAL, read the license yourself]), but I'm hesitant given that I have never heard anyones stories about production use.
> The self hosted license seems fairly permissive (Don't cluster, don't let your users manage the database views/queries [IANAL, read the license yourself])
The self-hosted version is being discontinued after the current version. The only offering will be the purely commercial cloud offering.
The self-hosted version is being discontinued after the current version. The only offering will be the purely commercial cloud offering.
Elasticsearch has some functionality that does this:
https://www.elastic.co/guide/en/elasticsearch/reference/curr...
More on the concept: https://en.wikipedia.org/wiki/Prospective_search
https://www.elastic.co/guide/en/elasticsearch/reference/curr...
More on the concept: https://en.wikipedia.org/wiki/Prospective_search
[deleted]
Potentially ignorant question: who is the intended persona for this product? Is this for people that are serving "data products" to end users but don't want to own and manually configure their caching layer? And the product is magic provided by some automated rollup tables and materialized views based off of the data it sees being used to most? Maybe I'm overthinking..
PolyScale founder here. Assuming you are referring to PolyScale (rather than ClickHouse), the product is aimed at devs who dont want to build data distribution and caching. You can connect your database and then have global low-latency reads, without writing code. Useful for multi-region deployments, serverless/microservices/FaaS as well as simply scaling your origin db.
ClickHouse is used for computing Observability metrics within the UI. The automated caching algorithms do not use ClickHouse in any way. You can read more about the automation here: https://docs.polyscale.ai/how-does-it-work#caching-protocol or try the live demo here: https://playground.polyscale.ai/
ClickHouse is used for computing Observability metrics within the UI. The automated caching algorithms do not use ClickHouse in any way. You can read more about the automation here: https://docs.polyscale.ai/how-does-it-work#caching-protocol or try the live demo here: https://playground.polyscale.ai/
“Modern” app development today usually presumes some element of “live updates” or “multiplayer” functionality. It’s usually handled only partially, in the app layer, with a good amount of spaghetti.
But the database to me seems like the place where this should happen. I should be able to
and then I should be able to subscribe to any changes to that query.
I should be able to have thousands of these subscriptions open at a time.
And ideally I should be able to get an efficient diff rather than a new result. Although a new result would be a great start.
I’m not sure why this isn’t seen as table stakes for databases in 2022. It seems like such a fundamental challenge of distributed application development.