Note: This post is intended as a supplement to WTF Just Happened? A Quick Tour of Your First Rails App.
MVC and Rails
Understanding the MVC pattern is key to understanding Rails.
MVC divides divides the work of an application into three separate but cooperative subsystems: models, views and controllers. At a high level, models labour behind the scenes, views are the smiling face at the front, and controllers are the masterminds behind it all.
- The browser sends a request to your Rails application.
- This request gets picked up by the Rails Router (see Rails Routing for more details).
- The router determines which controller action is responsible for responding to the request and it redirects it accordingly.
- If data is required from the database, the controller will request it from the model.
- The model will query the database to obtain the required data.
- It then returns the data back to the controller.
- The controller will then pass the data to the view and request the applicable template. The view takes the supplied data and uses it to generate a HTML document which it sends back to the controller.
- The controller will then return the requested resource back to the browser.
Models are classes that talk to your database. These classes inherit from
ActiveRecord::Base which provides them with all the standard functionality detailed in the Active Record architectural pattern.
They manage the relationship between your objects and the database. A model class encapsulates the business logic that is specific to your application through validation, association, transactions, and more.
The model subsystem is implemented in ActiveRecord, which provides an interface and binding between the tables in a relational database and the Ruby program code that manipulates database records. Ruby method names are automatically generated from the field names of database tables. This is one of the examples of what people refer to as "Rails Magic".
You can read more about Models in MVC: Model.
Controllers take user input (like a URL) and decide what needs to be done. The Controller layer handles incoming HTTP requests and provides a suitable response. Usually this response is in the form of a HTML document, but it may also be XML, JSON, PDFs, and more. It directs traffic and queries the models for specific data, and then organises that data (searching, sorting, messaging it) into a form that fits the needs of a given view.
You can read more about Controllers in MVC: Controller.
Views display the output. The View layer is responsible for the presentation of data in a particular format. It is composed of "templates" that provide representations of your application's resources. Usually these templates come in the form of a HTML document.
You can read more about Views in MVC: View.
There is a great easy-to-understand explanation of how Rails implements MVC in the README of the Rails repository on GitHub. You can read it here. Scroll about halfway down the page to the heading 'Welcome to Rails'.
Starting a New Ruby on Rails Project
Spree: Adding Custom Admin Tabs For New Resource
Detecting unused routes with Rails 7.1
reinteractive is Australia’s largest dedicated Ruby on Rails development company. We don’t cut corners and we know what we are doing.
We are an organisation made up of amazing individuals and we take pride in our team. We are 100% remote work enabling us to choose the best talent no matter which part of the country they live in. reinteractive is dedicated to making it a great place for any developer to work.
Webinars are our online portal for tips, tricks and lessons learned in everything we do. Make the most of this free resource to help you become a better developer.
The Ruby on Rails Installfest includes a full setup of your development environment and step-by-step instructions on how to build your first app hosted on Heroku. Over 1,800 attendees to date and counting.
The Ruby on Rails Development Hub is a monthly event where you will get the chance to spend time with our team and others in the community to improve and hone your Ruby on Rails skills.