Reading a lot of data from IndexedDB can be slow. Reading the data in batches helps, but it's not perfect because it requires querying for both keys and values separately, and doesn't allow you to read in reverse order. A proposal from the Microsoft Edge team aims to address these limitations with a new method called getAllRecords. And we'd love to have your feedback on it.
2025 update: there is now a getAllRecords API in IndexedDB which resolves some of the issues described in this post. Namely, you can now query in batches in descending order, and you can fetch both…