Laravel Stored Procedure Vs Inline query

It depends (as always!). I always am wary about extracting a lot of business logic to the database, e.g. stored procedures / views. It tends to hide business logic, and can sometimes be difficult to test.

However, there are use cases for Stored Procedures, especially where the amount and interdependency of work (queries), would favour using a Stored Procedure

as long as theres documentation somewhere (but again it forces people to actually read/maintain them) & this is in documentation you can go for stored procedure -

using laravel sometimes the functionality is abstracted ie when using Queues/Jobs/Events so sometimes you forget..

but it depends on easiness like mentioned above