Concurrent Ratelimit policy

Not applicable

i just want to know if there is a way we can make a request wait when implementing concurrent rate limit policy?

Solved Solved
0 5 152
1 ACCEPTED SOLUTION

NO, It's an anti-pattern of REST APIs.

APIs are in general stateless. You shouldn't be having any state by making them queue up / do retry.

Offload this functionality to client / backend system.

Hope it helps.

-------------------------------

Anil Sagar

5997-screen-shot-2017-11-23-at-75916-pm.png Learn Apigee Concepts in 4 Minutes HandsOn

View solution in original post

5 REPLIES 5

NO, It's an anti-pattern of REST APIs.

APIs are in general stateless. You shouldn't be having any state by making them queue up / do retry.

Offload this functionality to client / backend system.

Hope it helps.

-------------------------------

Anil Sagar

5997-screen-shot-2017-11-23-at-75916-pm.png Learn Apigee Concepts in 4 Minutes HandsOn

thanks @Anil Sagar I know this is an anti pattern but i want to know if there is a way, what i mean is if have allowed 5 connections for concurrent rate limit policy and all 5 are active, now when the 6 request comes, it ll not be served by backend, so until a connection gets dropped, can we make the 6 request? or what you suggest in this situation?

6 request *wait

@Ilyas shah , Concurrent rate limit policy is used to protect backend. It's not a quota policy. Increase the rate limit.

If counter is over the limit, Apigee drops the requests.

thanks @Anil Sagar I agree totally.