Why REST API is so slow compare to network request from Figma application

1. Request and Response Payloads

• REST API: REST APIs often involve larger payloads, especially if they are transferring substantial amounts of data or multiple resource types. The time required to serialize, send, receive, and deserialize these payloads can slow down performance.
• Figma Network Requests: Applications like Figma are optimized for specific types of data (e.g., design assets), and they often use optimized data formats and transfer protocols that reduce payload size and increase speed.

2. Overhead and Latency

• REST API: Each REST API request typically involves HTTP headers, status codes, and additional metadata, which can introduce overhead. Network latency, including DNS resolution and TCP handshakes, also affects API performance.
• Figma Network Requests: Figma and similar applications might use more efficient protocols (e.g., WebSocket for real-time updates) or employ content delivery networks (CDNs) to minimize latency and overhead.

3. Data Serialization and Parsing

• REST API: REST APIs commonly use JSON or XML, which require serialization and parsing. JSON parsing can be time-consuming, especially for complex or deeply nested data structures.
  Figma Network Requests:** Figma may use binary formats or efficient data encoding methods that are faster to serialize and deserialize compared to text-based formats.

4. Caching and Optimizations

• REST API: APIs might not always implement effective caching strategies. Without caching, every request results in a full network round-trip, which can be slow.
  Figma Network Requests:** Applications like Figma may use aggressive caching strategies, local storage, and data prefetching to reduce the need for repeated network requests.

5. Server and Application Design

• REST API: The performance of a REST API can be influenced by server-side factors such as database queries, server load, and the efficiency of the backend logic.
• Figma Network Requests: Figma’s network infrastructure and application design are optimized for fast data retrieval and real-time collaboration, which can make network requests appear faster.

6. Concurrency and Throttling

• REST API: APIs may have rate limits or throttling policies to prevent abuse, which can affect the response times if too many requests are made in a short period.
• Figma Network Requests: Figma’s network requests are likely optimized for high concurrency and handle many simultaneous connections efficiently.
  Summary

REST APIs can be slower than network requests from applications like Figma due to factors such as larger payloads, additional overhead, serialization and parsing time, lack of efficient caching, and backend server performance. Optimizing REST API performance often involves addressing these factors through techniques such as payload minimization, efficient data formats, and improved caching strategies.

Thanks for your reply. But I think this issue can only be solved by Figma…