Skip to content

Commit c04e28d

Browse files
committed
docs: restore original point 1 in Why QueryMode
1 parent 25b7d39 commit c04e28d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/src/content/docs/why-querymode.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Why QueryMode
33
description: Agents are the new users. They need dynamic pipelines, not pre-built ETL.
44
---
55

6-
1. **Agents are becoming the majority of internet traffic.** They serve different owners across different parts of the world, but share the same training data and independently reach the same conclusions. When thousands of agents hit the same endpoints at the same millisecond, the result is thundering herds that look like a DDoS — except every request is legitimate. That's not a DDoS attack. That's just Tuesday. When 10,000 agents ask the same question, regional Query DOs serve the cached result — that's a CDN problem, not a query engine problem. When they ask *different* questions, you need composable pipelines that didn't exist five minutes ago. QueryMode handles both.
6+
1. **Agents are becoming the majority of internet traffic.** They serve different owners across different parts of the world, but share the same training data and independently reach the same conclusions. When thousands of agents hit the same endpoints at the same millisecond, the result is thundering herds that look like a DDoS — except every request is legitimate. That's not a DDoS attack. That's just Tuesday. Data must live at the edge to survive this.
77

88
2. **Agents need live data.** Decisions based on outdated training data lead to bad outcomes. Training data can't keep up with the speed the world produces information. Agents make API calls for live data — lots of them. That data needs to live at the edge, close to where agents run.
99

0 commit comments

Comments
 (0)