A node is a node, it fails sometimes. So what happens when a RPC node fails? You can fail over - but that requires you to write some code to try next available node.

How about I tell you that I provide a Load balancing RPC Node that will automatically find the fastest route (a good one) and redirect the STEEM API calls for you?

Introducing the Load Balancing RPC Node: https://steem.justyy.workers.dev/

See the list of nodes: https://steemyy.com/node-status.php

https://steemyy.com/steemjs/

The candidate nodes:

Currently, I have added the following:

1
2
3
4
5

let nodes = [
"https://api.justyy.com",
"https://api.steemit.com",
"https://api.steemitdev.com",
];

So, the chance of all three nodes die - almost close to ZERO. That should give you some confidence of using it. The Load Balancer Node lives on the CloudFlare Edge - (yes, the serverless function)

Beware that this node returns different version number, sometimes 0.23.0 and sometimes 0.23.1!

Every little helps! I hope this helps!

Steem On!~

If you like my work, please consider voting for me, thanks!
https://steemit.com/~witnesses type in justyy and click VOTE

Alternatively, you could proxy to me if you are too lazy to vote!

Also: you can vote me at the tool I made: https://steemyy.com/witness-voting/?witness=justyy

Visit me at: https://steemyy.com

This page is synchronized from the post: ‘Introducing the Load Balancing RPC Node: https://steem.justyy.workers.dev/‘