Which rate limiting mechanisms apply to Deta Base under high concurrent request loads?

Concurrent Request Handling in Deta Base

Deta Space employs a serverless architecture where the frontend is decoupled from the backend storage. Data persistence is managed through Deta Base, a NoSQL-like document store accessed via a REST-based API.

When deploying Micro apps that require frequent state updates, the interaction between serverless functions and the Deta Base API becomes a primary performance bottleneck. Specifically, it is unclear how the platform manages request queuing or throttling when multiple concurrent requests target the same data store.

What are the specific rate limiting thresholds for Deta Base API endpoints during high-concurrency bursts? Does the platform implement a leaky bucket or fixed-window algorithm to handle these spikes?