lukoktonos

Readyset auto-parameterizes cached queries similar to a prepared statement. If you run the same query with different parameters, it will be routed to the cache. The first time a parameter set is queried, it will be a cache miss and trigger an "upquery" to populate the cache, after which that set of parameters will be served from the cache.

Different where clauses (sets of parameters) would map to different query-caches and currently need to be cached separately.

Aggregates supported by Readyset[1] will also be automatically maintained, but depending on the query, they may be handled by post-processing after retrieving results from a cache

[1] https://docs.readyset.io/reference/features/queries#aggregat...

We use Gerrit internally and use GitHub as a pseudo-mirror. We allow (and welcome!) community contributions to GitHub via PRs.

Our internal Changelists in Gerrit get synced to GitHub as those PRs you are seeing (the branch names correspond to Gerrit change-ids), and any community PRs get copied to our Gerrit first before going through CI and then being merged and synced with GitHub.

Readyset does have some work and design done towards read-your-writes consistency, but it's still under development. The Noria paper does briefly touch on extending partial materialization with stronger consistency models via MVCC or other mechanisms as well.

What do you mean by write support here? Readyset will apply writes via a replication stream from the upstream database.

I was agreeing with you that it seems overpriced and relying on a niche market that doesn't care about being cost effective hardware-wise.

I just bought a mini PC for $350 that has 32gb of ram, a windows 11 license, and is not much bigger than these devices by the looks of it.

People who find this small device useful must just not want to spend their (likely high $/hour) time with mundane things getting their expensive toy home servers working or something