{"id":315,"date":"2025-08-27T19:38:24","date_gmt":"2025-08-27T19:38:24","guid":{"rendered":"https:\/\/1v0.net\/blog\/?p=315"},"modified":"2025-08-27T19:38:26","modified_gmt":"2025-08-27T19:38:26","slug":"eager-loading-vs-lazy-loading-in-laravel-best-practices","status":"publish","type":"post","link":"https:\/\/1v0.net\/blog\/eager-loading-vs-lazy-loading-in-laravel-best-practices\/","title":{"rendered":"Eager Loading vs Lazy Loading in Laravel: Best Practices"},"content":{"rendered":"\n

Eager Loading vs Lazy Loading in Laravel: Best Practices<\/strong><\/h2>\n\n\n\n

When working with Eloquent relationships, performance issues often appear because of the \u201cN+1\u201d query problem. This happens when each record triggers additional queries for related data. Laravel provides lazy loading<\/strong> and eager loading<\/strong> to control how related data is fetched. In this article, you\u2019ll learn the difference between them, see code examples, and discover best practices for balancing performance and memory usage. We\u2019ll also build a simple profile UI that uses eager loading to display related posts efficiently.<\/p>\n\n\n\n

<\/div>\n\n\n\n

1 – Understanding Lazy Loading<\/strong><\/h2>\n\n\n\n

Lazy loading<\/strong> means related data is only loaded when you first access it. This keeps initial queries lightweight but can trigger many additional queries if you loop through related data.<\/p>\n\n\n

\/\/ app\/Http\/Controllers\/UserController.php<\/span>\nnamespace<\/span> App<\/span>\\Http<\/span>\\Controllers<\/span>;\n\nuse<\/span> App<\/span>\\Models<\/span>\\User<\/span>;\n\nclass<\/span> UserController<\/span> extends<\/span> Controller<\/span>\n<\/span>{\n    public<\/span> function<\/span> index<\/span>()<\/span>\n    <\/span>{\n        $users = User::all(); \/\/ single query for users<\/span>\n\n        foreach<\/span> ($users as<\/span> $user) {\n            \/\/ Each call triggers a separate query (N+1 problem)<\/span>\n            $posts = $user->posts;\n        }\n\n        return<\/span> view('users.index'<\/span>, compact('users'<\/span>));\n    }\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Here, User::all()<\/code> fetches all users. But every time $user->posts<\/code> is accessed in the loop, Laravel issues another query, leading to dozens or hundreds of queries\u2014this is the N+1 problem<\/em>.<\/p>\n\n\n\n
<\/div>\n\n\n\n
2 – Using Eager Loading<\/strong><\/h2>\n\n\n\n
Eager loading<\/strong> solves the N+1 problem by fetching related data in advance with one extra query. You use with()<\/code> to tell Eloquent which relations to load.<\/p>\n\n\n
\/\/ app\/Http\/Controllers\/UserController.php (improved)<\/span>\nnamespace<\/span> App<\/span>\\Http<\/span>\\Controllers<\/span>;\n\nuse<\/span> App<\/span>\\Models<\/span>\\User<\/span>;\n\nclass<\/span> UserController<\/span> extends<\/span> Controller<\/span>\n<\/span>{\n    public<\/span> function<\/span> index<\/span>()<\/span>\n    <\/span>{\n        \/\/ One query for users + one query for posts<\/span>\n        $users = User::with('posts'<\/span>)->get();\n\n        return<\/span> view('users.index'<\/span>, compact('users'<\/span>));\n    }\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Instead of dozens of queries, Laravel now runs two: one for users and one for posts. Relations are hydrated into each user automatically, eliminating N+1 overhead.<\/p>\n\n\n\n
<\/div>\n\n\n\n
3 – Nested Eager Loading<\/strong><\/h2>\n\n\n\n
You can eager load nested relations by passing arrays to with()<\/code>. Useful for dashboards that display multi-level data.<\/p>\n\n\n
\/\/ Fetch users with posts and each post's comments<\/span>\n$users = User::with(['posts.comments'<\/span>])->get();<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This runs three queries: one for users, one for posts, and one for comments. Eloquent maps everything together in memory, saving you from manually stitching queries.<\/p>\n\n\n\n
<\/div>\n\n\n\n
4 – Eager Loading with Constraints<\/strong><\/h2>\n\n\n\n
Use a closure inside with()<\/code> to filter related data. This prevents loading unnecessary rows.<\/p>\n\n\n
\/\/ Only load published posts for each user<\/span>\n$users = User::with(['posts'<\/span> => function<\/span> ($q)<\/span> <\/span>{\n    $q->where('status'<\/span>, 'published'<\/span>);\n}])->get();<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
Even though a user might have many posts in different statuses, only published ones are pulled into memory. This keeps responses small and efficient.<\/p>\n\n\n\n
<\/div>\n\n\n\n
5 – Lazy Eager Loading (N+1 Fix After the Fact)<\/strong><\/h2>\n\n\n\n
If you\u2019ve already loaded a collection without eager loading, you can still fix N+1 by calling load()<\/code> after the fact.<\/p>\n\n\n
$users = User::all();        \/\/ only users<\/span>\n$users->load('posts'<\/span>);       \/\/ now posts are fetched in one extra query<\/span>\n\nforeach<\/span> ($users as<\/span> $user) {\n    \/\/ no extra queries here<\/span>\n    foreach<\/span> ($user->posts as<\/span> $post) {\n        echo<\/span> $post->title;\n    }\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
load()<\/code> attaches the related models after the initial query, solving the N+1 problem if you forgot to use with()<\/code> upfront.<\/p>\n\n\n\n
<\/div>\n\n\n\n
6 – A Simple Profile UI Example<\/strong><\/h2>\n\n\n\n
Let\u2019s build a profile page that shows the user\u2019s information and their posts. We\u2019ll use eager loading to prevent N+1 queries.<\/p>\n\n\n
\/\/ app\/Http\/Controllers\/ProfileController.php<\/span>\nnamespace<\/span> App<\/span>\\Http<\/span>\\Controllers<\/span>;\n\nuse<\/span> App<\/span>\\Models<\/span>\\User<\/span>;\n\nclass<\/span> ProfileController<\/span> extends<\/span> Controller<\/span>\n<\/span>{\n    public<\/span> function<\/span> show<\/span>($id)<\/span>\n    <\/span>{\n        $user = User::with('posts'<\/span>)->findOrFail($id);\n        return<\/span> view('profile.show'<\/span>, compact('user'<\/span>));\n    }\n}<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This controller uses with('posts')<\/code> so both the user and their posts are loaded in only two queries.<\/p>\n\n\n
<!-- resources\/views\/profile\/show.blade.php -->\n@extends('layouts.app'<\/span>)\n\n@section('content'<\/span>)\n<div class<\/span>=\"container<\/span>\">\n  <h1<\/span>><\/span>{{ $user->name }}\u2019s Profile<\/h1>\n  <p class<\/span>=\"text<\/span>-muted<\/span>\">Email<\/span>: <\/span>{{ $user->email }}<\/p>\n\n  <h3 class<\/span>=\"mt<\/span>-5 mb<\/span>-3\">Posts<\/span><\/h3<\/span>>\n  @foreach<\/span>($user<\/span>->posts<\/span> as<\/span> $post<\/span>)\n    <div<\/span> class<\/span>=\"card<\/span> mb<\/span>-3\">\n      <div<\/span> class<\/span>=\"card<\/span>-body<\/span>\">\n        <h5<\/span> class<\/span>=\"card<\/span>-title<\/span>\"><\/span>{{ $post->title }}<\/h5>\n        <p class<\/span>=\"card<\/span>-text<\/span>\"><\/span>{{ Str::limit($post->body,120<\/span>) }}<\/p>\n      <\/div>\n    <\/div>\n  @endforeach<\/span>\n<\/div>\n@endsection<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
The Blade file prints user info and loops through their posts. Because we eager-loaded the posts in the controller, this page will always use a constant two queries, no matter how many posts exist.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Wrapping Up<\/h2>\n\n\n\n
Lazy loading is simple but can cause N+1 queries in loops. Eager loading (with()<\/code>) fetches related data in bulk and avoids performance pitfalls. Lazy eager loading (load()<\/code>) is handy when you already have a collection but need extra relations. By choosing the right loading method, you keep queries efficient and your app fast\u2014even with complex relationships.<\/p>\n\n\n\n
<\/div>\n\n\n\n
What\u2019s Next<\/h2>\n\n\n\n