pg_ivm VS readyset

FTA, because I don't like Jeopardy questions in headlines:

“Incremental View Maintenance (IVM) provides a method for keeping materialized views current by calculating and applying only the incremental changes, as opposed to the complete recomputation of contents performed by the REFRESH MATERIALIZED VIEW command.”

Article shows using the pg_ivm Postgres extension available here: https://github.com/sraoss/pg_ivm

There is an extension that provides some limited incremental MVIEW refresh: https://github.com/sraoss/pg_ivm

There’s awesome work being done on incremental view maintenance in postgres:

https://github.com/sraoss/pg_ivm

It makes sense to perform managed denormalization - use a materialized view or automatically refresh a table or foreign server (via FDW) using common triggers (like pg_ivm does). And it's fine to add a TTL to it and use as a read store... update on user login and make a partial index just for that. And that's how you could get CQRS...

- Some platforms like Supabase Realtime [3] and Firebase offer subscription models to database changes, but these solutions fall short when dealing with complex queries involving joins or group-bys.

My vision is that the modern frontend to behave like a series of materialized views that dynamically update as the underlying data changes. Current state management libraries handle state trees well but don't seamlessly integrate with relational or graph-like database structures.

The only thing I can think of is to implement it by myself, which sounds like a big PITA.

Anything goes, Brainstorm with me. Is it causing you headaches as well? Are you familiar with an efficient solution? how are you all tackling it?

[1] https://readyset.io/

Postgresql + MySQL Cache https://github.com/readysettech/readyset

I just wanted to give a high five for having Jepsen tests for this: https://github.com/readysettech/readyset/tree/stable-240117/...

This example is a great use case for partial incremental view maintenance systems like ReadySet: you automatically get something like the “prepopulating the cache” section (toward the end of the blog) while only caching the data the application is using, and avoiding the need to manually implement any sort of invalidation logic.

(Disclaimer: I used to work for them, but don’t anymore. It’s all available for free on GitHub though for anyone interested: https://github.com/readysettech/readyset)

There are systems that will do that for you like https://readyset.io/.

ReadySet

readyset.io is the company that jonhoo was associated with for work on noria

Might be interesting to try out https://readyset.io for this use case.

On the caching topic, I found the ReadySet(né Noria) approach to be extremely interesting.