Performance when dealing with an ever growing list of items

[Aculeo]

Hey, just a general question I'm wondering: If I have an application that stores (just an example) TODOs in local storage, a list will be ever-growing, how do you handle that? If you never delete items, merely archive them. Do you start splitting those lists up into separate "buckets", like one per year? Or do you keep a list of IDs and created date under one key, and the actual items as individual keys? Wondering what makes the most sense to keep the performance OK, even when you thousands of items. Also want to avoid loading everything into memory at once.

It's worth noting, I would never need to iterate over all items unless the user searches for something. If that takes a bit of time, that's OK.

[Aculeo]

After some more research, I'm beginning to think that local storage itself is probably the wrong tool for this. Perhaps IndexedDB is the answer. But I'm getting the impression that there aren't many Blazor WASM apps that store all data purely in the browser, with only an optional sync to a cloud.