Why caching reduces response times in Laravel - See It in Action

Why caching reduces response times in Laravel

📖 Scenario: You are building a Laravel web application that shows a list of popular books. Each time a user visits the page, the app fetches the book list from the database. To make the page load faster, you want to use caching to store the book list temporarily.

🎯 Goal: Build a simple Laravel controller method that fetches a list of books from the database and caches the result. This will reduce response times by avoiding repeated database queries.

📋 What You'll Learn

Create a variable with a list of books (simulate with an array)

Add a cache key name variable

Use Laravel's cache to store and retrieve the book list

Return the cached or fresh book list

💡 Why This Matters

🌍 Real World

Caching is used in web apps to store frequently requested data temporarily. This avoids repeated slow database queries and makes pages load faster for users.

💼 Career

Understanding caching is important for backend developers to optimize app performance and improve user experience.

1

Create the initial book list data

Create a variable called $books and assign it an array with these exact values: 'The Hobbit', '1984', 'Pride and Prejudice'.

Laravel

<?php

namespace App\Http\Controllers;

use Illuminate\Http\Request;

class BookController extends Controller
{
    public function index()
    {
        // Create the books array
        // Your code here
    }
}

Hint

Use square brackets to create an array with the exact book titles.

2

Add a cache key variable

Add a variable called $cacheKey and set it to the string 'popular_books' inside the index method.

Laravel

<?php

namespace App\Http\Controllers;

use Illuminate\Http\Request;

class BookController extends Controller
{
    public function index()
    {
        $books = ['The Hobbit', '1984', 'Pride and Prejudice'];
        // Define cache key
        // Your code here
    }
}

Hint

Use a simple string variable to hold the cache key name.

3

Use Laravel cache to store and retrieve the book list

Use Laravel's cache()->remember() method with $cacheKey and a closure that returns $books. Set the cache time to 60 seconds. Assign the result to a variable called $cachedBooks.

Laravel

<?php

namespace App\Http\Controllers;

use Illuminate\Http\Request;

class BookController extends Controller
{
    public function index()
    {
        $books = ['The Hobbit', '1984', 'Pride and Prejudice'];
        $cacheKey = 'popular_books';
        // Cache the books list for 60 seconds
        // Your code here
    }
}

Hint

Use cache()->remember() with a closure that returns the books array.

4

Return the cached book list

Add a return statement that returns the $cachedBooks variable from the index method.

Laravel

remember($cacheKey, 60, function () use ($books) {
            return $books;
        });
        // Return the cached books
        // Your code here
    }
}

Hint

Use a simple return statement to send the cached books back.

Practice

1. Why does caching reduce response times in Laravel applications?

easy

A. Because it stores data to reuse instead of recalculating or fetching again

B. Because it increases the number of database queries

C. Because it slows down the server to save energy

D. Because it deletes old data to free memory

Solution

1. Step 1: Understand caching purpose

   Caching saves data temporarily so the system can reuse it quickly without repeating slow tasks.

2. Step 2: Connect caching to response time

   By reusing saved data, Laravel avoids slow operations like database queries, making responses faster.

3. Final Answer:

   Because it stores data to reuse instead of recalculating or fetching again -> Option A

4. Quick Check:

   Caching = Reuse data fast [OK]

Hint: Caching saves repeated work to speed up responses [OK]

Common Mistakes:

• Thinking caching increases database queries
• Believing caching slows down the server
• Confusing caching with deleting data

2. Which of the following is the correct Laravel syntax to store a value in cache for 10 minutes?

easy

A. Cache::save('key', 'value', 10);

B. Cache::store('key', 'value', 10);

C. Cache::put('key', 'value', 10);

D. Cache::remember('key', 10, 'value');

Solution

1. Step 1: Recall Laravel cache put method

   Laravel uses Cache::put(key, value, minutes) to store data in cache for a set time.

2. Step 2: Match syntax with options

   Cache::put('key', 'value', 10); matches the correct method and parameter order for 10 minutes caching.

3. Final Answer:

   Cache::put('key', 'value', 10); -> Option C

4. Quick Check:

   Cache::put = store with time [OK]

Hint: Remember Cache::put(key, value, minutes) for caching [OK]

Common Mistakes:

• Using Cache::store or Cache::save which don't exist
• Confusing parameter order in Cache::remember
• Passing value as last parameter in Cache::remember

3. Consider this Laravel code snippet:

if (Cache::has('users')) {
  $users = Cache::get('users');
} else {
  $users = User::all();
  Cache::put('users', $users, 5);
}
echo count($users);

What will this code output on the second request within 5 minutes?

medium

A. 0

B. The number of users in the database

C. An error because Cache::get returns null

D. Nothing, it will timeout

Solution

1. Step 1: Analyze caching logic

   On first request, users are fetched from database and cached for 5 minutes. On second request within 5 minutes, Cache::has('users') is true, so cached users are returned.

2. Step 2: Understand output

   Since $users contains all users, count($users) outputs the number of users in the database.

3. Final Answer:

   The number of users in the database -> Option B

4. Quick Check:

   Cache hit returns users count [OK]

Hint: Cache::has true means data reused, count matches DB users [OK]

Common Mistakes:

• Assuming Cache::get returns null causing error
• Thinking count will be zero on cache hit
• Believing cache expires immediately

4. This Laravel code tries to cache a query result but causes an error:

$users = User::all()->toArray();
Cache::put('users', $users, 10);
$cachedUsers = Cache::get('users');
echo $cachedUsers->count();

What is the likely cause of the error?

medium

A. Cache::get returns an array, so count() method is undefined

B. User::all() returns a collection that cannot be cached directly

C. Cache::put requires the time in seconds, not minutes

D. The cache key 'users' is reserved and cannot be used

Solution

1. Step 1: Understand what Cache::get returns

   Laravel cache serializes data. When retrieving, it returns the original data type if serializable. User::all()->toArray() returns an array.

2. Step 2: Identify error cause

   If Cache::get('users') returns an array, calling ->count() causes error because arrays use count() function, not method.

3. Final Answer:

   Cache::get returns an array, so count() method is undefined -> Option A

4. Quick Check:

   Array from cache has no count() method [OK]

Hint: Remember arrays use count(), objects use ->count() [OK]

Common Mistakes:

• Thinking cache keys are reserved
• Confusing cache time units (minutes vs seconds)
• Assuming collections always stay as objects after caching

5. You want to cache a complex database query result in Laravel to reduce response time. Which approach best ensures the cache updates automatically when the underlying data changes?

hard

A. Avoid caching and always query the database

B. Cache the query result once and never update it

C. Use Cache::forever and rely on server restart to clear cache

D. Use Cache::remember with a short expiration time and clear cache manually after updates

Solution

1. Step 1: Understand cache invalidation needs

   To keep cache fresh, it must expire or be cleared when data changes.

2. Step 2: Evaluate options for automatic update

   Using Cache::remember with short expiration allows automatic refresh after time. Manual clearing after updates ensures cache stays current.

3. Final Answer:

   Use Cache::remember with a short expiration time and clear cache manually after updates -> Option D

4. Quick Check:

   Short expiry + manual clear = fresh cache [OK]

Hint: Short cache time plus manual clear keeps data fresh [OK]

Common Mistakes:

• Caching forever without update causes stale data
• Never clearing cache leads to outdated responses
• Avoiding caching misses performance benefits