IndexedDB sharding library feedback
Hi guys, I made an opensource library that handles sharding and am still working on setting up the readme and tutorials. Anyone that wants to check out my code and give feedback?https://github.com/BramPostema/indexeddb-sharding All the feedback is welcome.
GitHub
GitHub - BramPostema/indexeddb-sharding
Contribute to BramPostema/indexeddb-sharding development by creating an account on GitHub.
6 Replies
@ItsBrumm is my main acc. Working on my work laptop so not using that acc rn.
from a glance at index.ts the only part that sticks out to me is in updateItemById https://github.com/BramPostema/indexeddb-sharding/blob/1631e7dc016cb360c5f0579c2dc3edf10cba61b1/src/index.ts#L101
where you don't seem to handle case where the item is not found. is this an expected outcome? if not you could consider throwing an error or returning false to let the caller know. otherwise you should probably document it
GitHub
indexeddb-sharding/src/index.ts at 1631e7dc016cb360c5f0579c2dc3edf1...
Contribute to BramPostema/indexeddb-sharding development by creating an account on GitHub.
also +1 for Brum image
thx for calling it out. Ill make it throw an error if not found
Very confused as to why we need sharding for indexeddb
Indexed db gets slower when u get more and more items
I recommend keeping it under 250k items per database
I went from a day of inserting data to about 20 minutes by using sharding