> Egeria is in-memory for performance reasons
I dont see how this relates, as a relational DB can run in-memory, and overflow to SSD. And cache values for the "views".
Selecting rows from cache of a database is still 100-1000 times slower than reading numbers from an array. And dumping this array into a KV store is much easier than generating SQL.