This question already has an answer here:
We have a web infrastructure for serving a normal website that has some moderate file downloads (a few hundred K, up to a MB or two). We have a new requirement to start hosting larger files up to 100 or 200 MB. Bandwidth will be pretty light as these be restricted to relatively few users so it will be on the order of tens of downloads per day. Some folks in our group have raised hackles about these downloads eating up too many threads in our web servers and hence they should be moved to separate download site. I don't why our current infrastrucute wouldn't suitable or, at worst require a few more apache instances behind the load balancer. The files are behind access control which we would need to wire into an external download site creating more development effort. My question is does their argument hold water or am I correct? Or is there a middle ground where we can maybe throttle downloads to not chew up too many threads without standing up a new environment?