Level 75
Just a suggestion, but I would stick to MVC conventions in laravel.
Yes separation is pretty for us the developers. But when compiled and ran by the CPU is meaningless.
Oct 24, 2023
3
Level 4
DDD and Laravel
I have been studying DDD a bit and I really like the concept of having all the business logic centered on one place, also, the separation of application and infrastructure makes sense to me. I also like Laravel a lot. The problem is: I don't know how to combine both, or if they should be combined at all.
Usually, the nicest projects using DDD I see are the ones the have a clear separation of folders (domain, infra, application), but that seems a bit difficult with Laravel, so my question is: how can I separate my folder structure in Laravel in order to make it more DDD-friendly?
Level 4
@jlrdw I get it that MVC is nice, but it seems fit for CRUDS. Laravel does have the power to handle big projects and those projects usually seem better organized with DDD, for example. Also, I am not a CPU.
Level 73
I agree with @jlrdw, stick to convention, it will save you time and effort. I'm not saying it can't be done, but there is a reason for Laravel to be MVC.
1 like
Please or to participate in this conversation.