Where should I write business logic on laravel application ? (or any other MVC architecture)

@OussamaMater great videos !!

@OussamaMater thanks

Excellent , can you please explain , why controller should be skinny ?

I heard that , controllers should be like a bridge between models and view , but im not sure why ...

thanks

@leostereo let me give you a simple example.

You write some great code in a controller for getting a specific number of rows and transform it into a format you can use.. Now later you find out you actually need the same thing in a console command (artisan). So do you want to use that controller? It expects a request.. Console does not have requests.. And it returns a view.. But you don't want to use a view.. So you need to write exactly the same code again in the console command

@Sinnbeck thanks .... thanks .... Im thining that perhaps , taking code to helper / action claseses , same code can be used also by other controllers as well.

Speaking for myself, I tend to think of the controller code as the entry point to the logic, sort of the "main" function, which calls other things in a top/down way. If it needs to hit the database, I might add a method to the model. If it's making requests to a third party API, let's say Jira, I'll wrap all that stuff in a custom Jira service class. Miscellaneous other calls may go in a helper class or just a file with helper functions; could be a generic helper, or one dedicated to this particular topic/activity.

Typically this leaves the controller code as very short and readable, mostly making calls to methods/functions defined elsewhere.

@leostereo Well @jeffreyway has mentioned countless times, there are many ways to do things, and sometimes there is no "right way"

I know when I was programming in java, yes I normally had MVC. However for some things small I would sometimes use Servlet and view (CV).

Same in PHP, let it depend on what you are doing. I know many here put a bunch in the controller.

I normally don't, I do like @tray2 mentioned, smaller controller and fat models.

Doing a query to retrieve = model

A query to update, many times controller is fine.

And don't get stuck on some of those "patterns" I find that sticking to MVC is all that's needed. Yes implement DRY.

@leostereo

For example .... switch from laravel to YII reutilizing most of the model.

You would still have a lot of code rewrite, because Yii 2 ORM is still different from Laravel.

Whereas Using laravel getPdo() and Cake\Datasource\ConnectionManager it would be the exact same code, just a few tweaks are needed.

I have converted cake to laravel. But I use regular sql 75 percent of the time.

Edit:

Same with Yii 2, Yii 2 also of course has an instance, I have used like:

    public static function dbh()
    {

        try {
            $dbh = \Yii::$app->db;
            $dbh->open();
            return $dbh;
        } catch (PDOException $e) {
            throw new pdoDbException($e);
        }
    }

@jlrdw thanks , very clear!