warm wasp
I built an idiomatic ratelimiter middleware that contains ready to use gin, echo and go's http middlewares and is really easy to use.
It is still very basic and has little configurations. I implemented the sliding window counter algorithm but not exactly like the actual one.
I'd love if you suggest me some changes and features and also give me advice on making it better. And also give it a star if you liked it 🥺
harsh oar
Cool lib man, I like the simplicity and plug-and-play feel.
Just a heads-up though - naming it “Don't DDoS me daddy” is a bit misleading. Rate limiting won't help against a real DDoS attack (e.g. thousands of IPs flooding you). It’s useful for abuse protection or API quotas per IP/user, but not a defense mechanism against actual distributed denial-of-service.
warm wasp
Cool lib man, I like the simplicity and plug-and-play feel.
Just a heads-up tho...
Thanks for the info!
warm wasp
Cool lib man, I like the simplicity and plug-and-play feel.
Just a heads-up tho...
Banning the attackers ip won't help them cuz they will probably use proxy switcher
what's an effective way that companies actually use?
harsh oar
Banning the attackers ip won't help them cuz they will probably use proxy switch...
mostly WAF/network-level filtering
companies can also use anycast networks (traffic is distributed across global nodes)
there is a lot of things companies can do to fight against DDoS
warm wasp
there is a lot of things companies can do to fight against DDoS
Thanks again for the infos 