Queries per second is not only a server metric. In AdTech it is also a contractual and commercial boundary between supply, routing infrastructure and demand.
Why one global limit is insufficient
Search and XML workloads have different request shapes, economics and delivery paths. Nexus therefore models independent channel QPS values and supports member-level QPS structures for XML operations.
- Platform boundary
- Channel boundary
- Member boundary
- Service capacity
Caps versus QPS
QPS limits instantaneous rate. A cap limits volume over a longer operating or commercial period. Both may be required to prevent a fast source from consuming an entire allocation.
Governed configuration
Nexus keeps limits in validated tenant configuration and approved runtime records rather than exposing Redis or service credentials to the browser.
This guide describes Nexus product architecture and general AdTech operating concepts. Exact enforcement and integration behavior depends on the enabled revenue engine and agreed deployment configuration.