On 03/07/2013 04:34 PM, Grant wrote: >> Michael's proxy suggestion is excellent too - I use nginx for this >> a lot. It's amazingly easy to set up, a complete breath of fresh >> air after the gigantic do-all beast that is apache. Performance >> depends a lot on what your sites actually do, if every page is >> dynamic with changing content then a reverse proxy doesn't help >> much. Only you know what your page content is like. > > It sounds like having apache serve dynamic .html pages and nginx > serve images on the same port means turning apache into a proxy for > nginx which I'm hoping isn't too difficult. Could this pose any > problems for an ecommerce site?
> Changing completely from a user-facing apache to a user-facing nginx > sounds fraught with peril. Yet this is the way it's done. If you have apache serve as a proxy for nginx, you gain absolutely *nothing*; every inbound connection still takes Apache resources, and that's exactly what you need to introduce a proxy to alleviate. Think of it like phone lines. Let's say you're getting fifteen phone calls an hour. It's too much. You hire a secretary named nginx to screen your calls for you and handle the simple responses like "has he changed his mind?" You're *supposed* to have the secretary take all the calls, and then pass along the calls to you that really need your attention. If you stick apache in front of nginx, rather than the other way around, what you're instead doing is having everyone call you, and then put the secretary you hired on speakerphone while she takes the call...
signature.asc
Description: OpenPGP digital signature
