mongrel unicorn - Nov 2013 - Best way to deploy an internal Rack app?

Hello!

I have a Rails monolith and have identified a few parts which can be chipped off
and deployed as self-contained services, called by the monolith.

Each service will be a rack app presenting an API over HTTP.  For now everything
will run on the same box.  The services shouldn''t be exposed to the
outside world.

I have almost built the first service and am now wondering how best to serve it.
For example:

- Does Unicorn alone suffice or should I front it with Nginx?
- To keep the services internal do I just listen to a port on the loopback
interface?

Thanks in advance,

Andrew Stewart

_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying

Andrew Stewart <boss@airbladesoftware.com> wrote:
> Hello!
> 
> I have a Rails monolith and have identified a few parts which can be
> chipped off and deployed as self-contained services, called by the
> monolith.
> 
> Each service will be a rack app presenting an API over HTTP.  For now
> everything will run on the same box.  The services shouldn''t be
> exposed to the outside world.
> I have almost built the first service and am now wondering how best to
serve it.  For example:
> 
> - Does Unicorn alone suffice or should I front it with Nginx?
This depends on how you want clients to connect.  Either the unicorns
need to listen on different addresses/ports, or you can set up nginx to
handle routing so clients only connect to nginx.
> - To keep the services internal do I just listen to a port on the
> loopback interface?
Any address:port (127.0.0.1:1234, 127.0.0.2:1234, ...), or unix socket.
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying