Recent searches
Search options
@bw@social.lolWhat is the simplest solution for persisting user data?
I frequently run into a situation where I’ve built a neat little frontend app but need to persist some user data. My first instinct is to stick it in local storage, which is cool and totally works. But it’s at risk of being deleted by the browser and it’s not portable to other browsers or devices.
Things I’ve used:
- PHP/MySQL
- PHP/SQLite
- NodeJS/SQLite
- JSON files
- Userbase (third-party service)
- I’ve even used paste.lol as a BE
@bw What about PocketBase?
@jak2k Yeah I’m keeping my eye on this one. It looks great.
@bw I agree demo kv is probably the easiest and most flexible. Plus you run it yourself or have deno land run it. But that’s if a kv store is appropriate. If data is relational I’ve done SQLite as WAsM in deno for my Dropserver apps. Seems to work just fine though I wouldn’t do that if storing thousands of users data!
@bw Maybe not the simplest per se, but remoteStorage.js is still pretty simple for what it can do for your app:
@raucao Yeah I do like the idea of users bringing their own data storage. For one, it takes the responsibility off of me, the app developer, to keep everyone’s data safe.