Guides
Running the infrastructure, not just calling it
11 articles on getting, choosing, running, scaling and watching a node — general where the problem is general, and per chain where it is not. Written for the decisions that come before picking a provider from the rankings, and the ones that come after deciding not to.
Ethereum
BSC
Solana11 articles · page 2 of 2
- Running a nodeBSC
Running a BNB Smart Chain node
“Why does a BSC node need four times the machine?”
Hardware quoted from BNB Chain's own best practices, why snapshots are effectively mandatory, how much memory to hand the cache, and the method the public endpoints will not serve you.
- Running a nodeSolana
Running a Solana RPC node
“Is a Solana RPC node the same as a validator?”
No — and sizing one from validator requirements is the mistake that produces a node permanently behind the cluster. Hardware quoted from Anza, why the accounts and ledger need separate devices, and what account indexes cost.
- Running a node· All three chains
Exposing RPC without giving it away
“Can I just open the port?”
No. An open JSON-RPC port is an unauthenticated public interface to your node with no rate limit and no accounting — what to bind, what to put in front of it, and which namespaces never belong on a listener anybody else can reach.
- Scale· All three chains
Serving RPC at scale
“One node works. How do I serve real traffic?”
Load balancing that understands RPC, routing methods to the node that can answer them, what is safe to cache and what is not, and why failover between two providers is a different exercise from failover between two of your own nodes.
- Observability· All three chains
Knowing your node is healthy
“How do I find out it is broken before my users do?”
What to measure on a node you run — and what to measure on a provider you do not — including the four checks this platform performs on every endpoint, written out so you can run them yourself.