Hi,
On 22.04.2013 23:51, Bryan Talbot wrote:
> Since haproxy is not a webserver (it's a reverse proxy), you still
> need a webserver to actually serve content and run the application.
>
Indeed. I would prefer using varnish serving static files, so you can
cache them in memory.
thomas
> -Bryan
>
>
> On Mon, Apr 22, 2013 at 2:28 PM, S Ahmed <[email protected]
> <mailto:[email protected]>> wrote:
>
> My backend servers run jetty, and currently I am using nginx that
> runs on port 80 to route traffic to the backend that runs on e.g.
> port 8081.
>
> I also using nginx to serve the static files for the folder:
>
> /assets/
>
> So all requests that have this folder do net get proxied to jetty
> on port 8081, but nginx servers the static files.
>
> If I use haproxy now, do I still need to run nginx to service
> static files or is this something haproxy can do just as effeciently?
>
> I'd rather reduce the # of services I have to manage :)
>
>
