Hello all, I have always deploys rails apps with unicorn and nginx as a reverse proxy in the past. However, I am working with a new firm and they would like to use Apache with mod_pagespeed in front of unicorn.
We will be deploying a rails 3.1 app with streaming. To me, mod_pagespeed does not seem like a magic bullet, as it appears to be a collection of best practices which have to be rewritten as a page is being served. Why not code with the best practices in mind as to not have to scan and yet again reprocess the content? Searching on the web, I find few entries about mod_page speed and rails, and relatively few entries about apache with unicorn. To me it seems that using best practices, with appropriate use of caching, and nginx would be a better solution than apache with mod_pagespeed. Questions: 1) Does nginx provide any necessary services to unicorn, that apache cannot provide? 2) If apache can provide all necessary services, does it do them as well as nginx. 3) We would like the fastest user experience possible. Does apache with mod_pagespeed hold any weight here over nginx? 4) Part of a fast user experience is how fast you get the page, correct? Seems like nginx has the upper hand here, due to nginx's nio vs apache's threading. 5) Would it make since to put nginx in front of apache w/mod_pagespeed (or visa versa), to use the applicable mod_pagespeed filters? Or is this a bad idea to begin with? 6) Is there anything else I am missing? Are there any specific resources I need to look at? 7) Should we go with nginx or apache? (Opinions ok.) Much thanks, Matt Smith _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
