This makes me think, with the arrival of continuous querying: * kSQL' EMIT CHANGES * Spark has stream-stream JOINs * Flink's default behavior ('time-varying

This makes me think, with the arrival of continuous querying: * kSQL' EMIT CHANGES * Spark has stream-stream JOINs * Flink's default behavior ('time-varying relations') is to emit the changes * Materialize's value proposition is centered around event-streaming, and has Live Materialized Views. , is there a need for a client-side reactive SQL lib (react plugin?) where reactive data management would be done on continuous queries? If your client data is only a slice (CREATE VIEW slices AS SELECT .. JOIN .. ON .. = u.user_id [WHERE ..][GROUP BY ..]) of your server data, wouldn't it: * help a lot in cache management (as in: none to do. If you get reactive updates on changed data you don't need a cache) * help in moving client-side logic server-side, and vice versa (since it would be expressed in the same language) I mean: is there a market for it? Some people really do like SQL, I know I do.