MVC architecture in Laravel - Mini Project: Build & Apply

MVC Architecture in Laravel

📖 Scenario: You are building a simple Laravel web app to manage a list of books. You want to organize your code using the MVC (Model-View-Controller) pattern. This helps keep your code clean and easy to maintain.

🎯 Goal: Create a Laravel MVC structure where you define a Book model, a BookController controller, and a view to display all books.

📋 What You'll Learn

Create a Book model with a title and author property

Create a BookController with an index method to get all books

Create a Blade view file books/index.blade.php to show the list of books

Set up a route to connect the URL /books to the index method of BookController

💡 Why This Matters

🌍 Real World

Organizing web app code with MVC helps developers build clean, maintainable, and scalable applications.

💼 Career

Understanding Laravel MVC is essential for backend web development roles using PHP and Laravel framework.

1

Create the Book model

Create a Laravel model called Book with the properties title and author as fillable fields.

Laravel

<?php

namespace App\Models;

use Illuminate\Database\Eloquent\Model;

// Define the Book model with fillable properties
class Book extends Model
{
    // Your code here
}

Hint

Use the protected $fillable property to list 'title' and 'author'.

2

Create the BookController with index method

Create a Laravel controller called BookController with a public method index that retrieves all books using Book::all() and returns the view books.index passing the books as books variable.

Laravel

<?php

namespace App\Http\Controllers;

use App\Models\Book;
use Illuminate\Http\Request;

class BookController extends Controller
{
    // Your code here
}

Hint

Use Book::all() to get all books and return view('books.index', ['books' => $books]) to send data to the view.

3

Create the Blade view to display books

Create a Blade view file resources/views/books/index.blade.php that loops over the $books variable and displays each book's title and author inside an unordered list.

Laravel

Hint

Use Blade syntax @foreach ($books as $book) and display with {{ }}.

4

Add route for books index

In the routes/web.php file, add a route that maps the URL /books to the index method of BookController using Route::get.

Laravel

<?php

use Illuminate\Support\Facades\Route;
use App\Http\Controllers\BookController;

// Your code here

Hint

Use Route::get('/books', [BookController::class, 'index']) to define the route.

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