4 ms·
The use case is limited, a project has it's own backend, why need to add a new sub-system for tiny data storage?
by tcper 3y ago
The use case is limited, a project has it's own backend, why need to add a new sub-system for tiny data storage?
- buro9 3y agoI would state the opposite, the use case is huge. To add something new, that needs to persist, will not require going to a backend team and begging for a new API from them. A common difficulty is the simplest scenario, where do I store this frontend user preference? How do I store this that prevents nagging multiple times across devices? Backend teams will argue this is a frontend piece of data, and they provide APIs and backend storage that is agnostic of a specific frontend. This feels like a valuable addition.
- antifa 3y agoThis sounds like something that should just be an extra JSON column in the users table of any SQL database. Backend team shouldn't be withholding backend support if remembering this data is actually important.