CODEWITHSUNDEEP
ruby-on-railsrubynginxthin
Chris Dellinger
Chris Dellinger

Reputation: 2352

Distinguishing between nginx and thin

This is a newbie question around nginx and thin in the rails environment. In reading/learning on rails I frequently hear about nginx and thin being a great combination for a rails site. In reading the descriptions of each, they both describe themselves as web servers, so I'm a little confused at what the combination brings to the table. If anyone could briefly describe what they are and how they complement each other I would be greatly appreciative.

Thanks!

Upvotes: 13

Views: 3716

Answers (3)

Doel
Doel

Reputation: 984

Thin is an application server while Nginx is a web server.

From http://www.javaworld.com/javaqa/2002-08/01-qa-0823-appvswebserver.html

The application server exposes business logic to client applications through various protocols, possibly including HTTP. While a Web server mainly deals with sending HTML for display in a Web browser, an application server provides access to business logic for use by client application programs. The application program can use this logic just as it would call a method on an object (or a function in the procedural world).

Upvotes: 4

Alan Peabody
Alan Peabody

Reputation: 3557

A typical small application deployment will have Nginx(or Apache) and a handful of Thin(or Mongrel, Unicorn, etc) servers running all on one machine.

Nginx receives every request. It then serves and static files directly (css, js, images, cached stuff). If the request requires processing it then hands the request off to a rails process (Thin).

This way your (relatively) slow application servers are freed up from serving static files, and your web server is providing a sort of load balancing.

The benefit of Nginx/Thin over something like Apache/Mongrel is that Nginx/Thin can communicate directly via a unix socket, removing the overhead of communicating via the tcp/ip stack.

Upvotes: 25

Marcelo Cantos
Marcelo Cantos

Reputation: 185852

Speaking out of ignorance (I've never used Thin), it is quite normal to mix nginx and an application server together, using nginx to serve up static content and act as a reverse proxy for the application server.

This makes it easy to blend ludicrously fast static content serving with the application server of choice (which varies between programming languages), all coming from the same address:port.

Upvotes: 2

Related Questions