Separate rate limits for read and write endpoints
Are GET requests rate limited separately from POST and PATCH, or do they share the same bucket?
Are GET requests rate limited separately from POST and PATCH, or do they share the same bucket?
Same bucket today, GET and POST both draw from the same per-key limit, writes just tend to be heavier in practice. Splitting them is on the list but not scheduled yet.
Same bucket today, GET and POST both draw from the same per-key limit, writes just tend to be heavier in practice. Splitting them is on the list but not scheduled yet.
Makes sense, our write-heavy sync job was the one hitting limits first.
Would still like to see them split eventually, our read traffic is much higher than writes.
Makes sense, we adjusted our sync job to batch writes more aggressively in the meantime.
Would still like this split eventually but understand it is not urgent for most tenants.
Agreed this is lower priority than some of the other API work in flight, but it is on our radar.
Sign in to reply to this question.