Goal

You’ll understand what Rails actually is, the MVC pattern it’s built around, and the “convention over configuration” philosophy that genuinely shapes how every Rails app is structured.

Learn

Rails is a web application framework built on Ruby. It follows the MVC pattern (Model-View-Controller), separating an application into three distinct responsibilities:

• Model — represents data and business logic, typically backed by a database table
• View — the actual HTML/template shown to the user
• Controller — receives a request, coordinates with the model, and decides which view to render

A request flows through Rails in a predictable order: a URL hits a route, which maps to a controller action, which typically talks to a model, and finally renders a view.

Rails’ defining philosophy is “convention over configuration”: instead of requiring you to explicitly configure every detail, Rails assumes sensible defaults based on naming conventions. A model named User automatically maps to a database table named users. A controller named UsersController automatically looks for views in a folder called app/views/users/. This is genuinely different from many other frameworks, which require explicit configuration for these connections — Rails infers them from naming alone.

This means learning Rails involves learning its conventions, not just its syntax — code that doesn’t follow the expected naming pattern often simply doesn’t work “automatically,” requiring explicit configuration to override the convention, which is itself a meaningful signal you’re doing something Rails didn’t expect.

Decision Task

You create a model called Product in Rails. Before reading on: what will Rails automatically assume the corresponding database table is named, without you configuring anything explicitly?

Show Answer

products — Rails’ convention over configuration automatically pluralizes and lowercases the model name to infer the table name, with zero explicit configuration required. This is exactly the “convention” part of convention over configuration: Rails assumes this mapping by default, only requiring explicit configuration if you genuinely need to deviate from it.

Common Mistake

Fighting against Rails’ naming conventions unnecessarily — for example, naming a model something that doesn’t map cleanly to a sensible table name, then needing extensive manual configuration to make it work. Learning and working with Rails’ conventions (proper pluralization, expected folder structure) is usually far less work than fighting against them, since the framework is specifically built to reward following its expected patterns.

Practice Questions

1. What does the “M” in MVC stand for, and what is it responsible for?

Show Answer

Model — represents data and business logic, typically backed by a database table.

2. What does the “V” in MVC stand for, and what is it responsible for?

Show Answer

View — the actual HTML/template shown to the user.

3. What does the “C” in MVC stand for, and what is it responsible for?

Show Answer

Controller — receives a request, coordinates with the model, and decides which view to render.

4. What does “convention over configuration” mean, in your own words?

Show Answer

Rails assumes sensible defaults based on naming conventions, rather than requiring you to explicitly configure every connection between parts of the application.

5. If you create a controller called OrdersController, where would Rails automatically expect to find its views?

Show Answer

In a folder called app/views/orders/, following the naming convention linking a controller to its expected view folder.

Try It Yourself

Without looking back, explain in your own words the order a typical Rails request flows through, from URL to rendered page.

Show Answer

A URL is matched by a route, which maps to a specific controller action; that action typically interacts with a model to get or modify data, then renders a view (an HTML template) that gets sent back to the user’s browser.

Quick Check

1. What does MVC stand for?

Show Answer

Model-View-Controller.

2. What is a Model responsible for?

Show Answer

Representing data and business logic, typically backed by a database table.

3. What is a Controller responsible for?

Show Answer

Receiving a request, coordinating with the model, and deciding which view to render.

4. What does “convention over configuration” mean?

Show Answer

Rails assumes sensible defaults from naming conventions, rather than requiring explicit configuration for standard connections.

5. If a model is called User, what table name does Rails automatically assume?

Show Answer

users