- https://www.eigenmagic.com/2025/01/14/banning-bots-with-nginx-maps/
- https://idiallo.com/blog/zipbomb-protection
- https://fabulous.systems/posts/2025/05/anubis-saved-our-websites-from-a-ddos-attack/
- https://www.eigenmagic.com/2025/01/14/banning-bots-with-nginx-maps/

Github repo:
- https://github.com/anyflow/my-cluster/tree/main

DNS cache
- https://www.anyflow.net/sw-engineer/istio-dns-proxying#cb880816-dae9-4a73-aa17-c91570fe1317

I recently encountered a behaviour in Nginx that I didn’t expect and caused a production outage in the process. While I would love to blame DNS for this, as it’s usually the cause of most network-related issues, in this case, the fault lies with Nginx.

act

additional:

• https://www.reddit.com/r/devops/comments/15eb5e0/saved_more_than_30_compute_cost_by_switching_to/

linuxgsm ideas

kong config ideas