This doesn't help with optimistic UI updates though. The article is less about remotely executing SQL, but more about having a relational data model as a cache

This doesn't help with optimistic UI updates though. The article is less about remotely executing SQL, but more about having a relational data model as a cache in the frontend. However, when sending the query through to the backend on a cache miss, would be useful to only allow queries that have been extracted like so. Its similar to how Apollo does query [caching][1]. I really like it! [1]: https://www.apollographql.com/docs/apollo-server/performance/apq/ https://www.apollographql.com/docs/apollo-server/performance...