You can use an associated resource throttling policy to prevent excessive contention between related resources. This contention can make resources unavailable.
Two resources are associated when they have a dependency or contend for the same resource. For example, read and write operations on the same database field contend with each other. A high read speed can slow down write operations, and vice versa. If these operations contend freely, the resulting overhead reduces overall throughput. Associated resource throttling prevents this excessive contention.
Example
The read_db and write_db resources represent database read and write operations, respectively. Set the following rule for read_db to prioritize write operations. For more information, see Configure throttling rules for common scenarios.
When write operations to the database are too frequent, read requests are throttled. Calls to read_db are rejected when the Queries Per Second (QPS) of the write_db resource exceeds 10.