I often hear the term ‘middleware’ in the context of Ruby on Rails. What exactly is it? Can you provide specific examples?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I often hear the term ‘middleware’ in the context of Ruby on Rails. What exactly is it? Can you provide specific examples?
Middleware is related to Rack, the standard Ruby API for web applications. Since Rails applications are Rack applications these days, they apply to both.
Rack middleware is everything between application servers (Webrick, Thin, Unicorn, Passenger, …) and the actual application, such as your Rails application. It is the pipeline between the web application server and the application itself.
The input to a Rack application is an “environment” which contains all the HTTP request details (and more). The output is a HTTP response. Middleware layers are like filters which can modify the input, the output or both. Rails uses middleware to implement some of its features (query caching, cookie stores, http method expansion), but you can add your own.
Rack middleware is an effective way to reuse simple web-related behavior across web applications that use Rack, regardless of the underlying framework. If a part of your application adds functionality, but is not responsible for a HTTP response, it qualifies as Rack middleware.
Some examples of things you could implement as Rack middleware include:
See also this SO question.