I would love to see more databases support something like this. “Live queries” kind of thing.
“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
SELECT * FROM projects
WHERE owner_id=x
ORDER BY name desc
LIMIT 20
OFFSET 60;
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.
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.
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.
> 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.
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.
“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.