Baoyuantop commented on issue #13027: URL: https://github.com/apache/apisix/issues/13027#issuecomment-3956274220
Hi @MadhuTiwari-345, thank you for this excellent and detailed feature proposal. Your analysis of the limitations of static rate limiting thresholds is spot on. In production environments, traffic patterns can be highly dynamic, and an adaptive approach that responds to each consumer's baseline behavior would be a powerful addition to APISIX's traffic management capabilities. We agree that this feature would significantly improve security posture against abuse and reduce the operational overhead for gateway administrators. The high-level workflow you've outlined -- tracking a baseline, detecting spikes, and dynamically adjusting limits -- is a very logical and solid foundation for implementation. Regarding the implementation direction, creating a new, separate plugin (e.g., `adaptive-limit`) seems like a clean approach. It would promote modularity and avoid adding too much complexity to the existing rate-limiting plugins. For the backend, supporting both shared memory for single-node deployments and Redis for cluster-wide consistency is a great idea. This is a valuable and significant feature for the community. We encourage you and other community members to further discuss the specific algorithms for baseline calculation and anomaly detection. For instance, we could consider simple moving averages (SMA) or exponential moving averages (EMA) and weigh their trade-offs. We would welcome a design document or even a proof-of-concept if you are interested in contributing further. This is a fantastic proposal, and we look forward to seeing it develop. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
