3 ms·
Decoupling the storage from the application provider would be a huge step forward. Even if you continue to host your data on Dropbox or Google Drive, you have
by superb-owl 3y ago
Decoupling the storage from the application provider would be a huge step forward.
Even if you continue to host your data on Dropbox or Google Drive, you have total control over the underlying data--you can audit, modify, or delete it at any time.
From the application side, it also means you no longer have to deal with persistent state, which means you can ship applications with no backend. That's an order of magnitude easier to develop and maintain.
The downsides are real though: the user experience is often jankier, and the lack of a central database makes it really hard to do anything social/realtime. I'm rooting for Solid but am not yet convinced they'll make it.
- wmf 3y agoIn reality apps would keep their own cache and indicies of your data for faster and more reliable access.
- regularfry 3y agoSo there's an immediate consistency problem the user may or may not have the tools to fix because they rely on the application exposing a bespoke cache refresh. Is this solved for in solid?
- chrismatheson 3y agowasn't this a problem for http? any private network could funnel traffic through a reverse proxy cache and you end up with (potential) issues. Seemed to work ok for HTTP in general?