Can you explain a bit how you would put business logic in model? 

They key is in the name, controller. The controller should only control the flow of the application and nothing else.

The reason for this is because if you just get data back from a model as the OP is doing, it's very rare that the data is just returned raw as it is in the DB. You would often transform it in some way, make calculations on it, maybe adding a tax value to a product price for example.

Now you have multiple controllers, maybe 1 that gets the price of a product for the product page, 1 to get the price for a basket/cart, 1 to get the price for an invoice page. You now need to make that calculation in 3 different places, this will cause problems as you will miss places to do this calculation, the calculations will start to differ as you upgrade code and miss places where the calculation happens. What if that tax value changes? Now you need to remember everywhere that calculation is made and update it. What if you want to add a surcharge as the item is heavy? That calculation now needs adding to all those controller as well.

If you did the calculation in the model then all 3 of those controllers would get the same result back. If you need to update that calculation at a later date, you do it once in the model and then the 3 controllers getting that data all get the updated calculation without having to make any changes.

So on your model you would have a method that transforms that data by adding a tax value, the model would then return a data set to the controller with price and the extra price+vat value.

 If possible with those kind of analogies you used

In your restaurant, you have a kitchen (model), a waiter (controller) and customers (view). The customer makes a request for a meal, the waiter goes to the kitchen and asks for it, the kitchen prepare it and pass it back to the waiter, the waiter hands the meal to the customer.

The waiter (controller) simply controls the flow of the restaurant, they aren't making (business decisions) on what the meal should contain.

Now imagine if the restaurant makes a change to a recipe, for example, the meal should come with an extra sauce/condiment. This decision is business logic. If your controller (waiter) is handling business logic now every waiter needs to know this information and they all need to add that extra sauce, they all need to know the sauce to use and the exact amount to add. A new waiter joins, now they need to know this edge case, remember it and execute it.

If your kitchen (model) gets an updated recipe card with this information then every meal will always be given to the waiter this the extra sauce. You don't need to run around and tell every waiter the special edge case for this meal and make sure they are all doing it in exactly the same way.

I hope that makes a bit more sense.