Concrete advantages of the Eloquent ORM

Here you go:

• https://medium.com/@webmaster.laravelexpert/10-significant-advantages-of-laravel-application-development-78c2f04c9d07
• https://www.quora.com/Why-should-I-use-Eloquent-ORM-instead-of-Query-Builders-in-Laravel-when-both-on-an-end-convert-to-RAW-query-to-interact-with-DB-What-are-the-comparative-advantages-of-Eloquent-ORMs

The advantages is mostly nice looking code. For example

public function show($id)
{
    $book = Book::findOrFail($id);
    return view('books.show')->with('book', $book);
}

and

public function store(Request $request)
{
   $this->validateGenre($request);
   $genre = new Genre();
   $genre->genre = $request->genre;
   $genre->save();
}

To do the same thing in sql with the db facade would look something like

public function show($id)
{
    $book = Db:select('SELECT * FROM books WHERE id = ?', [$id]);
    return view('books.show')->with('book', $book);
}

public function store(Request $request)
{
   $this->validateGenre($request);
   DB::insert('INSERT INTO genre (id,  genre) values (?, ?)', [null, $request->genre]);
}

Eloquent makes some things easier but eloquent can not do it all.

It boils down to the right tool for the job or query in this case.

But remember anyting eloquent does is converted to normal SQL at runtime.

But remember even if you have a complex query that maybe eloquent won't handle you still have the DB facade in which you can write any query. And there's also getPdo (), which is the PDO instance.

For me, its a case of writing code that reflects what I am trying to do in my application, not code that SQL requires.