This is a great point and the reason why I think server-side rendering will ultimately fail.
I've done something similar for a site I manage (6groups.com). Each client's DB log is stored in compressed files on the server and only initialized via sqlite wasm on the client when needed. The trick is to periodically run compaction jobs (also on the client) to make sure DB logs don't grow to unreasonable sizes
I can't imagine the DB consumption I'd have if all client data was in relational format on the server
This is a great point and the reason why I think server-side rendering will ultimately fail.
I've done something similar for a site I manage (6groups.com). Each client's DB log is stored in compressed files on the server and only initialized via sqlite wasm on the client when needed. The trick is to periodically run compaction jobs (also on the client) to make sure DB logs don't grow to unreasonable sizes
I can't imagine the DB consumption I'd have if all client data was in relational format on the server