Routing Strategies
Explore the routing strategies available in Tatum’s RPC Gateway and learn how to use them to control traffic flow across your connected RPC endpoints.
Available Routing Strategies
The RPC Gateway offers two routing strategies & an Intelligent Data Routing power up to control how traffic flows across your connected RPC endpoints—each designed for different reliability, performance, and data-freshness needs. These strategies determine which endpoint receives your request and how the Gateway chooses between multiple providers..
Priority Failover
Ideal for maximum reliability. Priority Failover sends all traffic to your primary endpoint and automatically switches to the next one if it becomes slow, lagging, or unhealthy.
Load Distributed
Best for balanced performance across multiple providers. Load Distribution spreads traffic across all active endpoints using weighted round‑robin, ensuring no single provider is overloaded.
Update Gateway (Popular 🔥)
PATCH /v4/manage/gateway/{id}
Update routing in an existing gateway by using the endpointRouting parameter.
Priority Failover
Priority Failover is designed for teams that want maximum reliability and a predictable primary provider. In this mode, all requests are routed to your highest-priority endpoint. The Gateway continuously monitors its health and automatically redirects traffic if issues arise.
How It Works
- Primary-first routing: All requests go to Endpoint #1 (your chosen primary provider).
- Automatic failover: If the primary endpoint becomes unresponsive the Gateway immediately switches traffic to the next healthy endpoint in the list.
- Automatic recovery: Once the primary endpoint becomes healthy again, traffic is seamlessly routed back without any manual intervention.
Endpoint Ordering
You have full control over priority by dragging and dropping endpoints to reorder them in your Gateway. The topmost endpoint becomes your primary provider.
Load Distributed
Load Distributed routing is built for developers who want balanced performance across multiple RPC providers. This mode spreads requests across all active endpoints to avoid overloading any single provider.
How It Works
- Equal-weight distribution (current): Right now, traffic is distributed evenly across all healthy endpoints. Each provider receives the same share of requests.
- Health-aware rotation: If an endpoint becomes unhealthy, it is automatically removed from the rotation until it recovers.
- Dynamic weights (coming soon): In the future, you’ll be able to assign custom weights to endpoints—letting you send more traffic to faster, cheaper, or higher-capacity nodes.
Updated about 3 hours ago