Why chose ZAN Sui Data？
30%–60% average speedup
Retrieve the number on demand + associate it once to return once, reducing serial requests and duplicate fields, and faster above the hood of the list/details page
40%–70% fewer API calls
From 'multiple interfaces' to 'all fields at once', the benefits are obvious, especially on combination pages such as asset pages, transaction details, and activity flows
Replace core endpoints in 1–3 day
Keep the front-end data structure stable, and the back-end interfaces converge from multiple endpoints to the schema, reducing maintenance and co-commissioning costs
More stable in production
Provides query cost/time-consuming observation and current throttling policies to prevent a single complex query from slowing down the overall service
200–500ms update experience
It is suitable for scenarios where 'users are waiting for results' such as price alerts, transaction statuses, asset changes, and alarms
50% fewer polling requests
From 'pulling every 2–5 seconds' to 'pushing only when there is a change', significantly reducing QPS and bandwidth consumption
Resumable consumption
Supports incremental catching up from checkpoint, reduces the risk of data loss, suitable for indexing/real-time pipelines
Gradual replacement
Change the most critical 'event/object change' to subscription first, and continue to use json-rpc for the rest of the pages, which reduces the migration risk
Suitable for a variety of use scenarios
DeFi application
Real-time monitoring of liquidity pool changes and transaction events
NFT market
Tracking NFT's minting, transfer and sale events
Game application
Monitoring game-related assets and state changes in real-time
Wallet service
Building high-performance blockchain wallets and asset management tools
Data analysis
Deep analysis of chain data to build business intelligence platforms
Monitoring and alarm
Real-time monitoring of key indicators to respond to abnormal situations