---
title: "Comment by Saravana Thiyagarajan on \"Attack or massive usage?\" | Hashnode"
description: "I am not sure. You could also consider a rate-limiters based on the unique IP. It could prevent you from system outage."
url: "https://hashnode.com/posts/attack-or-massive-usage/65c29725b265a691d8301678/comment/65c3233e5a485fda94fd5cbe"
---

[Discussion](https://hashnode.com/posts/attack-or-massive-usage/65c29725b265a691d8301678)

Comment [Attack or massive usage?](https://hashnode.com/posts/attack-or-massive-usage/65c29725b265a691d8301678)

[Saravana Thiyagarajan](https://hashnode.com/@Saravana-Thiyagaraja)

[Feb 7, 2024](https://hashnode.com/posts/attack-or-massive-usage/65c29725b265a691d8301678/comment/65c3233e5a485fda94fd5cbe)

I am not sure. You could also consider a rate-limiters based on the unique IP. It could prevent you from system outage.

[Saeed Vaziry](https://hashnode.com/@saeedvaziry)

[Feb 7, 2024](https://hashnode.com/posts/attack-or-massive-usage/65c29725b265a691d8301678/comment/65c3233e5a485fda94fd5cbe#reply-65c3339662a81551fd0dfb20)

If you mean a rate-limiter in the app, I already have it. The thing is the requests are keeping the web server busy. But if you mean a rate-limiter on the CF itself then I can say not a use case for a business built based on rate-limit 😅
