Laravel Faster to query everything in controller or view

Question

Is it faster to query everything in the controller and return every query back, or query in view as you use it?

Assuming all the models had the relationship

Example:

Do everythig in cotroller and then return

Public function articlesHome($id)
{
$art = Articles::find($id);
$cit = Articles::city();
$tag = Articles::tags();
Return view('articles', compact('art', 'tag', 'cit');
}

Or in view (after controller returned $article)

{{ $article->name }}
...
{{ $article->city->name }}
...
@foreach($article->tags as tag)
{{ tag->name }}
@endforeach

Which is best in practice and faster.

Arthur Samarcos · Accepted Answer · 2015-08-07 13:44:32Z

2

Performance wise it's just a matter of finding a way to get fewer database queries to achieve the same result.

A good approach would be let laravel do it for you in a single command:

Public function articlesHome($id)
{
    $article = Articles::whereId($id)->with('city','tags')->get();

    Return view('articles', compact('article');
}

Your view would be the same. The articles relationships is already built, so no extra queries will be made.

{{ $article->name }}
...
{{ $article->city->name }}
...
@foreach($article->tags as tag)
{{ tag->name }}
@endforeach

answered Aug 7, 2015 at 13:44

Arthur Samarcos

3,29924 silver badges25 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

CIZO · Accepted Answer · 2015-08-06 11:22:51Z

A good pattern to read up on is MVC which stands for Models, Views and Controllers.

It's a design pattern that focuses of Separation of Concerns, where you separate the different concerns of your applications into different sections. The data retrieval is the Model (typically a database but not necessarily), a View (the Blade templates) and the Controller.

You can go beyond just MVC and separate things further to include Repositories, Events & Commands for a better separation.

The reason you might want to use Repositories (which are just wrappers around your Model) is to abstract the actual retrieval and persistence of your data from your Controller, allowing you to change from using a database to another form of strange without having to update the code in your controllers.

Jose Palazuelos · Accepted Answer · 2015-08-07 13:28:56Z

1

I assume it is faster to do it in the view as long as you save time sending it to the view. I recommend you that you install laravel debugbar to see the details.

answered Aug 7, 2015 at 13:28

Jose Palazuelos

1372 silver badges8 bronze badges

Collectives™ on Stack Overflow

Laravel Faster to query everything in controller or view

3 Answers 3

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related