MVC architecture in Laravel - Step-by-Step Execution

Concept Flow - MVC architecture in Laravel

User Request

↓

Routes

↓

Controller

↓

Model

↓

View

↓

Response to User

This flow shows how a user request moves through Laravel's MVC: routes direct to controllers, which use models to get data, then pass it to views for display.

Execution Sample

Laravel

<?php
// Route
Route::get('/users', [UserController::class, 'index']);

// Controller
class UserController extends Controller {
  public function index() {
    $users = User::all();
    return view('users.index', ['users' => $users]);
  }
}

This code handles a user request to '/users', fetches all users from the database via the model, and sends data to the view for display.

Execution Table

Step	Action	Component	Data/State	Output/Next Step
1	User visits '/users' URL	User	Request: GET /users	Route matches '/users'
2	Route calls controller method	Route	Calls UserController@index	Controller method invoked
3	Controller fetches all users	Controller	Calls User::all()	Receives collection of users
4	Model queries database	Model	Executes SQL SELECT * FROM users	Returns collection of users
5	Controller passes data to view	Controller	Data: users collection	View 'users.index' rendered with data
6	View generates HTML	View	Renders user list HTML	HTML sent as response
7	Browser receives HTML	User	Displays user list page	User sees list of users
8	End of request cycle	System	No further action	Request complete

💡 Request cycle ends after view renders and response is sent to user

Variable Tracker

Variable	Start	After Step 3	After Step 4	After Step 5	Final
users	undefined	Collection of User objects	Collection of User objects	Passed to view	Used in HTML output

Key Moments - 3 Insights

Why does the controller call the model instead of querying the database directly?

The controller uses the model to keep code organized and separate data logic from request handling, as shown in step 3 and 4 of the execution table.

How does the view get the data it needs to display?

The controller passes the data to the view as variables (step 5), so the view can use it to generate HTML (step 6).

What role do routes play in MVC?

Routes connect user URLs to controller methods, directing the flow of the request as seen in step 2.

Visual Quiz - 3 Questions

Look at the execution table, at which step does the model query the database?

A Step 4

B Step 5

C Step 3

D Step 2

💡 Hint

Check the 'Component' and 'Action' columns in the execution table for database queries.

According to the variable tracker, what is the state of 'users' after step 4?

A Array of user data from DB

B Collection of User objects

C Undefined

D Passed to view

💡 Hint

Look at the 'After Step 4' column for the 'users' variable in the variable tracker.

If the route did not exist for '/users', what would happen in the execution flow?

A Controller would still be called

B View would render empty data

C Request would stop at routing with an error

D Model would query database anyway

💡 Hint

Refer to step 2 in the execution table where the route directs the request.

Concept Snapshot

MVC in Laravel:
- Route receives user URL and directs to Controller
- Controller handles logic and calls Model for data
- Model interacts with Database
- Controller sends data to View
- View renders HTML for user
Keep these parts separate for clean code.

Full Transcript

In Laravel's MVC architecture, a user request starts at the routes which map URLs to controller methods. The controller acts like a middleman, asking the model to fetch data from the database. The model runs the database queries and returns data. The controller then passes this data to the view, which creates the HTML page the user sees. This separation keeps code organized and easy to manage. The execution table shows each step from user request to response, and the variable tracker follows how data changes. Key moments clarify why controllers use models and how views get data. The quiz tests understanding of these steps.

Practice

1. In Laravel's MVC architecture, which component is responsible for handling user input and application logic?

easy

A. Controller

B. Model

C. View

D. Route

Solution

1. Step 1: Understand MVC roles

   Model handles data, View handles UI, Controller handles logic and user input.

2. Step 2: Identify the component for logic

   Controller processes requests, applies logic, and returns responses.

3. Final Answer:

   Controller -> Option A

4. Quick Check:

   Logic and input handling = Controller [OK]

Hint: Controller = logic and input handler in MVC [OK]

Common Mistakes:

• Confusing Model with Controller
• Thinking View handles logic
• Assuming Route handles logic

2. Which of the following is the correct way to define a route that calls the show method of UserController in Laravel?

easy

A. Route::get('/user/{id}', [UserController, 'show']);

B. Route::get('/user/{id}', 'show@UserController');

C. Route::get('/user/{id}', function() { UserController@show(); });

D. Route::get('/user/{id}', 'UserController@show');

Solution

1. Step 1: Recall Laravel route syntax

   Routes use Route::get('uri', 'Controller@method') format for controller methods.

2. Step 2: Match correct syntax

   Route::get('/user/{id}', 'UserController@show'); matches this pattern exactly; others have syntax errors or wrong order.

3. Final Answer:

   Route::get('/user/{id}', 'UserController@show'); -> Option D

4. Quick Check:

   Correct route syntax = Route::get('/user/{id}', 'UserController@show'); [OK]

Hint: Use 'Controller@method' string in routes [OK]

Common Mistakes:

• Using array without quotes
• Swapping controller and method order
• Using anonymous function incorrectly

3. Given this Laravel controller method, what will be the output when accessing /welcome route?

public function welcome() {
    $name = 'Alice';
    return view('greeting', ['name' => $name]);
}

Assuming the greeting.blade.php view contains:

<h1>Hello, {{ $name }}!</h1>

medium

A. Error: Undefined variable $name

B. Hello, Alice!

C. Hello, $name!

D. Hello, !

Solution

1. Step 1: Understand data passing to view

   The controller passes ['name' => 'Alice'] to the view as variable $name.

2. Step 2: Interpret Blade template output

   The view uses {{ $name }} which outputs 'Alice' safely inside <h1> tags.

3. Final Answer:

   <h1>Hello, Alice!</h1> -> Option B

4. Quick Check:

   Passed variable rendered correctly = <h1>Hello, Alice!</h1> [OK]

Hint: Variables passed to view appear as {{ $variable }} [OK]

Common Mistakes:

• Expecting raw variable name output
• Confusing PHP variable syntax inside Blade
• Assuming missing variable error

4. Identify the error in this Laravel controller method:

public function index() {
    $users = User::all;
    return view('users.index', compact('users'));
}

medium

A. Missing parentheses after all() method

B. Incorrect view name syntax

C. compact() should be replaced with array()

D. User model not imported

Solution

1. Step 1: Check method call syntax

   User::all is a method and requires parentheses: User::all() to fetch all users.

2. Step 2: Verify other parts

   View name and compact usage are correct; import is assumed correct or handled by namespace.

3. Final Answer:

   Missing parentheses after all() method -> Option A

4. Quick Check:

   Method calls need () = Missing parentheses after all() method [OK]

Hint: Remember to add () when calling methods [OK]

Common Mistakes:

• Forgetting parentheses on method calls
• Misusing compact() function
• Assuming view name syntax error

5. You want to display a list of products with their categories in a Laravel app using MVC. Which approach correctly follows MVC principles?

hard

A. Use Controller only to render HTML, fetching done in View

B. Write SQL queries directly in the View to get products and categories

C. Fetch products and categories in Controller, pass to View, and display there

D. Put all fetching and HTML rendering inside the Model

Solution

1. Step 1: Recall MVC responsibilities

   Model handles data, Controller handles logic and data fetching, View handles display.

2. Step 2: Evaluate options

   Fetch products and categories in Controller, pass to View, and display there correctly fetches data in Controller and passes it to View for display, following MVC.

3. Final Answer:

   Fetch products and categories in Controller, pass to View, and display there -> Option C

4. Quick Check:

   Controller fetches, View displays = Fetch products and categories in Controller, pass to View, and display there [OK]

Hint: Controller fetches data; View only displays it [OK]

Common Mistakes:

• Putting SQL in Views
• Mixing data logic in Models with display
• Letting Views fetch data