> For the complete documentation index, see [llms.txt](https://tryflux.gitbook.io/flux-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tryflux.gitbook.io/flux-docs/8.-performance-and-scalability.md).

# 8. Performance & Scalability

#### 8.1 Database Design

MongoDB's document model supports:

* Efficient user scoping and query filtering
* Natural representation of nested run and receipt data
* Flexible schema evolution for new agent types or features

#### 8.2 Background Job Architecture

Vercel cron routes provide:

* Scheduled, reliable agent tick evaluation
* Horizontal scalability without managing job queues
* Built-in failure recovery and logging

#### 8.3 API Rate Limiting

Shared HTTP layer manages:

* Throttling on Uniswap API calls
* Exponential backoff for transient errors
* Circuit breakers to prevent cascade failures

#### 8.4 Real-Time Updates

Client-side polling and server-pushed updates via:

* WebSocket-ready architecture (future enhancement)
* Efficient delta updates to minimize bandwidth
* Cacheable metrics and snapshots


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://tryflux.gitbook.io/flux-docs/8.-performance-and-scalability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.