How to Choose a Sui Node Provider for Production Apps

Quick Recommendation: What to Look for in a Sui Node Provider

Before diving into the details, here is a concise checklist to guide your provider evaluation. Use it as a filter when comparing options.

• Protocol support: Does the provider offer both JSON-RPC and gRPC? gRPC is essential for high-throughput applications that need efficient streaming and lower overhead.
• Data availability: Do you need archive data for historical queries? Not all providers offer full archival access, which can be critical for analytics or compliance.
• Reliability and redundancy: Does the provider offer an SLA and multiple endpoints for failover? Production apps should not rely on a single point of failure.
• Scalability: Can the provider handle traffic spikes, such as NFT mints or token launches? Check if they offer dedicated nodes or auto-scaling.
• Pricing model: Understand how you are billed—per request, per compute unit, or monthly. Transparent pricing helps avoid surprises.
• Support: Is 24/7 support available? For production, you need a provider that responds quickly to incidents.

If you are evaluating providers, start by checking these criteria against your workload. For a managed solution that supports Sui, explore OnFinality's Sui network page and RPC pricing.

Why Sui Node Providers Matter

Sui is a high-performance Layer 1 blockchain designed for parallel execution and low latency. Its unique architecture, based on the Move language, enables fast transaction processing, but it also places specific demands on node infrastructure. Running a Sui full node yourself is possible, but it requires significant hardware, ongoing maintenance, and careful monitoring. For many teams, using a professional node provider is more practical, especially when you need reliable uptime, global distribution, and advanced features like gRPC or archive data.

The Sui documentation itself advises against using public endpoints for production due to rate limits. Instead, it recommends using dedicated nodes or shared services from professional providers. This is where a node provider becomes essential.

What to Evaluate in a Sui Node Provider

When comparing Sui node providers, focus on the following technical aspects that directly affect your application's performance and reliability.

JSON-RPC vs. gRPC

Sui supports both JSON-RPC and gRPC. JSON-RPC is the standard for most Web3 applications, but gRPC offers better performance for high-throughput use cases, such as real-time data streaming or indexing. Not all providers support gRPC, so if your application relies on it, you need to verify provider compatibility.

Archive Data and Historical Queries

If your application needs to query historical state, such as past transactions or account balances at a specific block, you need an archive node. Archive nodes store the entire history of the chain, which can be resource-intensive. Providers may offer archive access as an add-on or with higher-tier plans. Assess your needs: if you only need recent data, a full node may suffice.

Redundancy and Failover

A single RPC endpoint is a single point of failure. For production, you should have multiple endpoints, ideally from different providers, to ensure high availability. Some providers offer built-in failover or load balancing across multiple nodes. Consider how you will handle provider outages and whether the provider offers a robust SLA.

Performance and Throughput

Sui's high throughput means your RPC provider must handle a large number of requests without throttling. Look for providers that offer dedicated nodes or generous rate limits. Also, consider geographic distribution: endpoints closer to your users reduce latency.

Comparing Sui Node Providers: A Practical Table

Here is a comparison table to help you evaluate providers based on common criteria. Remember to verify current offerings, as features and pricing change.

Note: The table is illustrative. Always check the provider's official documentation for the latest features.

How to Connect to a Sui Node Provider

Once you have chosen a provider, you will typically receive an RPC endpoint URL. Here is an example of how to make a JSON-RPC call to a Sui node using curl:

curl -X POST https://rpc.sui.io \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "sui_getLatestCheckpointSequenceNumber",
    "params": [],
    "id": 1
  }'

Replace https://rpc.sui.io with your provider's endpoint. For OnFinality, you can find the public endpoint on the Sui network page.

Using WebSocket for Real-Time Updates

For real-time updates, such as transaction notifications, you can use WebSocket. Here is a JavaScript example using the websocket library:

const WebSocket = require('ws');

const ws = new WebSocket('wss://rpc.sui.io');

ws.on('open', function open() {
  ws.send(JSON.stringify({
    jsonrpc: '2.0',
    method: 'sui_subscribeTransaction',
    params: [],
    id: 1
  }));
});

ws.on('message', function incoming(data) {
  console.log(data.toString());
});

Again, use your provider's WebSocket URL.

Common Pitfalls When Using Sui Node Providers

Avoid these common mistakes to ensure a smooth experience:

• Using public endpoints in production: Public endpoints are rate-limited and unreliable for high traffic. Always use a dedicated or shared service.
• Ignoring gRPC support: If your application requires high throughput, not having gRPC can be a bottleneck.
• Not planning for failover: Relying on a single provider can lead to downtime. Set up multiple endpoints.
• Underestimating archive needs: If you need historical data, ensure your provider offers archive nodes.
• Overlooking pricing details: Some providers charge per compute unit, which can be unpredictable. Understand your usage patterns.

Troubleshooting: When Your Sui RPC Calls Fail

If you encounter issues, here are common symptoms and fixes:

Key Takeaways

• Sui node providers are essential for production apps due to the limitations of public endpoints.
• Evaluate providers based on protocol support (JSON-RPC/gRPC), archive data, redundancy, and pricing.
• Always plan for failover and use multiple providers for critical applications.
• Understand your workload to choose the right plan and avoid unexpected costs.

Frequently Asked Questions

What is a Sui node provider?

A Sui node provider offers managed infrastructure to interact with the Sui blockchain via RPC endpoints, handling node operation, maintenance, and scaling.

Do I need a dedicated node for Sui?

If your application has high traffic or requires consistent performance, a dedicated node may be necessary. For smaller projects, a shared service might suffice.

How do I choose between JSON-RPC and gRPC?

Use JSON-RPC for standard interactions. If you need high throughput or real-time streaming, consider gRPC if your provider supports it.

Can I use public Sui endpoints for production?

No, public endpoints are rate-limited and not recommended for production. Use a professional provider.

What should I do if my provider has an outage?

Have a failover plan with multiple endpoints from different providers. Monitor your endpoints and switch automatically if possible.

For more information on RPC providers and pricing, visit OnFinality's RPC pricing and supported networks.