QPS governance for advertising infrastructure

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.

Illustrative incoming and outgoing traffic

Suppose 1,000 incoming requests per second are each routed to two eligible partners, producing 2,000 outgoing requests per second. This is illustrative arithmetic, not a customer result, a routing promise or a performance benchmark. Nexus prices the incoming QPS, not the sum of incoming and outgoing traffic.

• For QPS-priced modules, capacity billing is based on incoming QPS. Outgoing QPS is unlimited for this billing calculation only; technical capacity, partner limits and configured operating caps still apply. This billing statement does not remove the separate daily click limits for XML / JSON feeds and OpenRTB. This does not redefine Search or CPA daily-capacity pricing.
• Check each partner’s own rate limits and integration contract before increasing fan-out.

Daily clicks are a separate capacity limit

For XML and OpenRTB, 1,000 incoming QPS allows a maximum of 10,000,000 clicks per day; 2,000 QPS allows 20,000,000. Each module and each location has its own limit. Unused capacity in one location does not cover another. This XML/RTB daily click rule is not a Video plan limit.

• XML / JSON feeds and OpenRTB each have a maximum of 10,000,000 clicks per day for each 1,000 incoming QPS block, independently per module and per location. At 2,000 incoming QPS, that module in that location has a maximum of 20,000,000 clicks per day. These limits cannot be pooled across modules or locations. This daily click limit applies only to XML / JSON feeds and OpenRTB, not VAST Video; Search and CPA keep their separate daily-capacity pricing. This is a plan limit, not an automatic technical stop. Higher daily click volumes require a capacity increase. Reaching the limit currently triggers no automatic action; arrange the capacity change with Nexus.