Make sure that nodes can handle traffic spikes

RevokeCash / revoke.cash

❌ Revoke or update your token approvals

https://revoke.cash

MIT License

674 stars 238 forks source link

Make sure that nodes can handle traffic spikes #109

Closed rkalis closed 1 year ago

rkalis commented 1 year ago

Recent updates have caused a higher node usage (no longer using injected provider + requesting blocks for timestamp). This means that we're getting close to Infura limits on "regular" days, making it hard to handle more active days.

Some potential solutions:

Pre-emptively upgrading Infura plan
Switching to an auto-scaling node provider like QuickNode or Alchemy
Adding Fallback providers in case Infura limits are reached
Finding a way to bring down number of requests

rkalis commented 1 year ago

Almost all other providers have too strict rate limits to be usable in the way Revoke is currently set up (i.e. many concurrent RPC requests). So it seems like upgrading Infura + bringing down requests is the way to go.

rkalis commented 1 year ago

I upgraded the Infura plan and enabled auto-scaling. For some other chains we use Alchemy, which also has auto-scaling enabled. So we shouldn't be running into any issues when traffic spikes.

The only issue is that we're relying on Etherscan's APIs for several chains, such as BSC and Fantom. Those chains may run into performance issues. For BSC we're subscribed to the highest plan, so I don't foresee any issues.