The author of Noria, Jon Gjengset, gave a great talk about the system: <a href="https://www.youtube.com/watch?v=s19G6n0UjsM" rel="nofollow">https://www.youtube.com/watch?v=s19G6n0UjsM</a><p>The speeds achieved are impressive but you do not get consistency.
+1 for anything that schematizes caching semantics<p>I've gotten this wrong so many times, and because it only bites you in read-after-write scenarios, it can be difficult to catch with types + tests<p>feels like there are a bunch of patterns in client-server protocols that should be 'as declarative as the schema', but aren't currently. caching, sync, field transformation, batching rules, multi-RPC flows like oauth
I could see this being very useful. The standard cache + db architecture has some sharp edges that end up biting people all of the time e.g. the thundering herd problem.
Noria is great research. Though, for anyone wanting to play with it for new projects, be aware that Jon (the author) has said that it's basically research-quality software, and the point was more to be a proof of value rather than to build a new production database.