3 ms·
There are lots of good reasons that go beyond content caching (which is the topic of the article). Somewhat terse write-up here: http://joshua.schachter.org/20
by pvg 17y ago
There are lots of good reasons that go beyond content caching (which is the topic of the article).
Somewhat terse write-up here:
http://joshua.schachter.org/2008/01/proxy.html http://joshua.schachter.org/2008/01/proxy.html
The basic idea is that there's fair bit of useful logic that can be handled by a simpler, lighter-weight, more easily securable front-end system than the lumbering tank that is your app server. This includes basic load balancing/failover, partitioning (requests of type foo go to these servers, all the low-latency ajax stuff over there, static content somewhere else), babysitting slow clients, blackholing malformed requests, etc.