Re: Reverse Proxy for Node.JS on IBM i

[Mark D <mdlkml@xxxxxxxxxxxxxxxx>]

For what it's worth you can proxy websockets through nginx in addition 
to regular traffic.  We have a nice hybrid setup going on where nginx 
handles some content, express static handles some other and express 
handles the rest.

Thanks,
Mark


On 12/26/2014 02:10 PM, Nathan Andelin wrote:
> Kelly,
>
> You seem to be headed down the right path. Your rationale for using NGINX
> or Apache as a reverse proxy sounds reasonable. You can configure the
> Apache server to forward requests to say a pool of Node.JS servers, if
> that's what you're thinking.
>
> You never mentioned any interest in web socket support. Web sockets would
> be a good use of Node.JS, and something that I'm interested in. But you may
> have other interests.
>
> For those of us who are interested in supporting web socket clients, I
> would use the web sockets interface to connect directly to a Node.JS
> server, rather than attempting to pass through a separate HTTP server
> instance.
>
> I have been reading more about NGINX, none of which has convinced me that
> the architecture performs or scales any better than Apache. In fact, it
> seems less scalable, especially with regards to static content.
>
> The NGINX event-loop is just terminology for establishing a connection and
> sending an HTTP request to a server. Apache uses a thread pool to manage
> connections, while NGINX apparently uses something of a queue methodology,
> to channel requests to separate processes (JOBS).
>
> Nathan.