We've actually been tinkering a lot early on with ways to make Epsio views more consistent (for example to block reads until the view processed all previous transactions), but saw most use cases people were using us for didn't require that level of consistency.

Usually we've seen companies use Epsio views for queries that can show data that is "a-bit" behind (usually sub second) similar to running on a read replica, and monitor the latency separately using datadog or something similar... Re readyset - they are also eventually consistent based on docs :)

@miikka.bsky.social So one of the fun things of being integrated with the database is that we can measure the time between a commit to the base table (sent via the replication stream) and our commit to the results table. We expose this metric for each view and strongly recommend monitoring it!