At some point it would probably make sense to look into changing this into a HAF app. That would have eliminated all the issues you had with account history fetches and batching, because you would have a database that you could create custom queries on. It does come with storage costs, of course (unless you get someone to host the HAF server for you and run your app there).
You are viewing a single comment's thread from:
I was thinking of using the browser's local storage to cache data to reduce the burden on the nodes, before seeing HAF. Though, I do have a bigger issue going on right now. Each pending curation reward is calculated by using get_content, so that equals thousands of calls to the node. I guess HAF also could solve that, right?
Yes, you would be able to create your own API calls, so you could create a single call that met your needs. If your app is already dependent on a lot of hivemind-based API calls, one option would be to use the HAF-based hivemind that we'll be releasing soon, then adding your own custom call support to that.