You are viewing a single comment's thread from:
RE: Steem Data Analysis: Who Withdraws Rewards vs Builds SP?
You could just implement a failover logic in your code to try a different RPC node - alternatively you can use the following load balancers:
- https://steem.justyy.com (USA)
- https://api.steemyy.com (UK)
Or, you can set up a node your self: https://github.com/DoctorLai/steem-load-balancer
Hi, thank you for your response. I didn't know about this repo: https://github.com/DoctorLai/steem-load-balancer, so I really appreciate you sharing it with me.
I actually built my own solution for load balancing as well. I also make sure to pass to the next API call only if the current one doesn’t fail.
As for finding accounts with withdrawn Steem Power (SP) and checking power-up status, I'm using the API from SteemWorld. It provides direct results within the data range I need.
I could implement the same solution using RPC, but it would return more results and take much longer to process, since there’s no method to directly fetch powered-up accounts or accounts without SP. I would need to use
get_account_historywith pagination and scan the data within the desired range.Regarding load balancing, if I were to balance across all the RPCs, it would be quite a lot. There are 3,657,270 users, so calculating requests would look like this:
3,657,270 * 2 + 365,727 = a huge number of requestsManaging that many requests and handling the load balancing is a bit too much. Hosting this would likely result in my IP getting blocked eventually, which is why it feels frustrating.