yii2中的速率限制与使用nginx进行速率限制 [英] rate limit in yii2 vs using nginx for rate limiting

问题描述

通过yii2进行速率限制与使用nginx作为反向代理和速率限制器之间有什么区别?

what is difference between rate limiting via yii2 versus using nginx for example as reverse proxy and rate limiter ?

REF: Yii2限速API

推荐答案

应用速率限制(例如yii2)更加灵活.例如，您可以为每个用户写不同的限制.或将请求放到队列中以备将来执行.但是，超出此限制的每个请求仍会命中PHP脚本.

Application rate limit (like yii2) more flexible. You can write different limits per user, for example. Or put request to some queue for future execution. But each request over that limit still hit PHP scripts.

Nginx的灵活性较差，但允许在PHP脚本之前停止请求.

Nginx limits less flexible, but allow to stop request before PHP script.

Nginx限制通常用作DOS保护.通常的任务:例如，不允许从一个IP产生太多的PHP进程.

Nginx limits usually used as DOS protection. Usual task: do not allow to spawn too much PHP processes from one IP, for example.

应用程序速率限制用作应用程序后端过载保护.它可以是数据库或外部API.此外，应用程序限制可以用作业务逻辑的一部分(不同关税计划的不同费率限制等)

Application rate limit used as application backend overloading protection. It's can be database or external API. Also, application limits can be used as part of business logic (different rate limits for different tariff plans, etc)

这篇关于yii2中的速率限制与使用nginx进行速率限制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！