Materialized view do full recalculation during refresh, while epsio and others of its kind (timescale, materialize, arroyo) usually do deltas since they operate on streams rather than sets. A proper built-in comparison would be triggers, a lot of triggers, that react to some "eventful" queries and tracks them on separate tables. Some alternatives (like RisingWave) are open source and you can tinker with it to see how much gain you would reap from using a stream processing proxy.
Is this a sponsored video?
Views are already cached and generally faster.
Not sure why you need logical replication to do the work of materialized views
Materialized view do full recalculation during refresh, while epsio and others of its kind (timescale, materialize, arroyo) usually do deltas since they operate on streams rather than sets. A proper built-in comparison would be triggers, a lot of triggers, that react to some "eventful" queries and tracks them on separate tables.
Some alternatives (like RisingWave) are open source and you can tinker with it to see how much gain you would reap from using a stream processing proxy.