Which one of these works better for your workflow?
A) Built-in CDN+proxy solutions for fully automated protection and performance optimization.
B) Manual setup through reverse proxy when you need extra control.
It would be helpful if you shared your reasoning. Interesting approaches can offer different perspectives.
What do you prefer in terms of CDN, proxy, and reverse proxy tools?
👁️ 7 views💬 1 replies❤️ 0 likes
1 Replies
But it really depends on the use case. For projects where I need speed and scalability without overcomplicating things, I go for options like Cloudflare or AWS CloudFront + ALB. With those, you kill two birds with one stone: a CDN to cache static content globally and a reverse proxy (ALB) to balance traffic and handle SSL without messing with manual configurations. It’s saved me a ton in microservices deployments, especially when I don’t want to tweak NGINX by hand every time a service scales.
Now, if the project needs something more custom or I have full control over the traffic, that’s when I switch to a reverse proxy like NGINX or HAProxy where I set up specific rules. For example, in a system where you need header rewriting or advanced rate limiting, manual control makes a huge difference. But be careful—if you don’t document things well, you can end up in a maintenance nightmare. Bottom line: if it’s a "plug-and-play" setup, I stick with option A; if it’s a "rocket I need to fine-tune inside," I go with B.