[Dancer-users] factory recommendation for web server

[Adam Taylor]

Historically, in the days of mod_perl; Apache, when loaded with  
mod_perl and whatever else required is pretty bloated and heavy.

Thus using a whole Apache + mod_perl to serve static content is just  
overkill and hence the idea to chuck a nimble webserver in front (e.g.  
nginx).

One reason for splitting frontend and backend servers, these days,  
could be so you could scale your stack horizontally rather/as well as  
just buying a beefier machine.

Also, it might be fun to play with shiny things :)

But, yes, it probably does make it more complicated if you don't  
require it. That said, I'm not sure how well/if nginx can handle Perl  
on it's own.

Sent from my iPhone

On 4 Jan 2011, at 20:08, Puneet Kishor <punk.kish at gmail.com> wrote:

> My question is thus -- why need two different servers? Can't Nginx  
> do everything? After all, Dancer doesn't serve and content. Dancer  
> creates the content, or routes the web server to the correct  
> content. It is the web server that serves the content. Doesn't  
> having one web server serve static content and the other serve  
> Dancer generated content make your web application more complicated?