![]() Great! So raise the spike arrest to 10000 RPS and you are done. Our backend system can handle 10 calls at the same millisecond and it is a For your configuration, this doesn't sound like a lot but when we are talking about systems with a setting of 500RPS, it can have a huge negative impact. For instance, if Apigee Edge behaved the way you are requesting, depending on which rate limiting algorithm was chosen, there is a chance that a backend system could actually receive more traffic (burst traffic) per second than what it could actually handle. Rather, the purpose of the policy is to prevent sudden spikes in traffic and to prevent DDOS attacks. The spike arrest policy does not keep a counter and is not intended to be used as a business policy to specify how much traffic your business clients should send per-time-interval. Note: there is no per-second option for quota. If you want to ensure your clients don't exceed your exact specified amount, it sounds like 600 RPM would do it for you. ![]() Then use a quota policy to implement a per-minute business restriction. Yes, raise your spike arrest policy to a value that is meant to limit what your backend can handle just before it begins degradation. Your APIs and backend can handle a certain amount of traffic, and the Spike Arrest policy helps you smooth traffic to the general amounts you want. Rather than as a way to limit traffic to a specific number of requests. Please read the docs on the Spike Arrest policy here as the documentation clearly lays out what the spike arrest policy is used for.įrom the docs: Think of Spike Arrest as a way to generally protect against traffic spikes A critical deployment is just pending for this logic to be implemented. I'm ok to have a complex custom implementation too as I'm desperately looking for this feature. for a very long time.ĭoes anyone have any suggestions to solve this problem? On a tail note, its kind of sad that apigee doesn't support this feature which has been available in IBM Datapower, WSO2, Axway API Gateway, etc. Is it still allowed? I don't seem to make it work as there is an error when I try to save the proxy on Edge UI. I do see that in some old documentation from apigee where second is allowed as a valid value.The Quota timeunit never allows second as a valid value.I've looked at Quota policy which can simply act as a counter. ![]() I have also looked ConcurrentRateLimitPolicy and apparently, it is logical that it doesn't serve my requirement.In my situation, our backend system can handle 10 calls at the same millisecond and it is a valid scenario for us to handle (Not considered as a Spike). ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |