I ran into the IndexedDB slowness problem while adding support for it to Converse.js XMPP messenger[1]. I'm using localForage which lets me persist data to eit

I ran into the IndexedDB slowness problem while adding support for it to Converse.js XMPP messenger[1]. I'm using localForage which lets me persist data to either sessionStorage, localStorage or IndexedDB (depending on user configuration), however writes to IndexedDB were excruciating slow. I didn't want to give up on it however, because localStorage has a storage limit that power users were constantly coming up against, and IndexedDB is also necessary for progressive web apps. Eventually I solved the problem by batching IndexedDB writes with a utility function I wrote called mergebounce[2]. It combines Lodash's "debounce" and "merge" functions to combine multiple function calls into a single one, while keeping and merging the data that was passed to the individual function calls. That way, you can call a function to persist data to IndexedDB many times, but it only executes once (after a small delay). I wrote a blog post about this approach[3]. It's generic enough that anyone else who uses localForage for IndexedDB could use it. 1. https://conversejs.org https://conversejs.org 2. https://github.com/conversejs/mergebounce https://github.com/conversejs/mergebounce 3. https://opkode.com/blog/2021-05-05-mergebounce-indexeddb/ https://opkode.com/blog/2021-05-05-mergebounce-indexeddb/