Re:Ask HN: How has IndexedDB been holding up for you in prod...
by throwaway9103 on Sunday February 09, 2020 @06:49PM
(#22285176)
Thank you for your input. I recall reading somewhere before about a chrome update that (accidentally?) wiped out data stored through indexeddb. Have you heard or experienced anything like this? That case is more concerning to me than when a user clears their own data, because any copies of the data across many machines would all be wiped out around the same time.
Re:Ask HN: How has IndexedDB been holding up for you in prod...
by no_wizard on Sunday February 09, 2020 @07:21PM
(#22285364)
I’ve experienced updates in every browser go awry in this way one way or another.
It’s really built to be a source of ephemeral storage not the sole provider for an application, that’s just the reality of it. There’s no continuity guarantees.
Re:Ask HN: How has IndexedDB been holding up for you in prod...
by throwaway15392 on Sunday February 09, 2020 @08:49PM
(#22285754)
I see... that’s not good
It also has a concept of versioning that’s really clean.
However, all your data is dead if you ever clear your cache or migrate machines. You should really consider that as a huge downside. Databases have an important use case and you don’t have to just use a SQL solution either.
Something like CouchDB would work fine if you only want some Storage. PouchDB + CouchDB is a good combo That would give you some nice abstractions here without having to put all the onerous on the end user to have some continuity in their data
Also see https://developers.google.com/web/fundamentals/instant-and-o...