Software engineering engineer at a national public broadcaster. Best practices / developer experience / agile / diversity and inclusion / psychological safety
It's true it's not easy to use DDD in Laravel without rebuilding a lot of systems from the ground up. I'm tryring to find a middle ground here so we can use DDD & UML and bring some consistency to the hot mess Laravel apps tend to become after a few years 😅
I think they get along pretty well. There is like a 5 minute process to add a domain folder that is autoloaded and you are pretty much ready to go. There are packages that helps you get even further very easily. Personally I really like github.com/lunarstorm/laravel-ddd - It's a very lightweight DDD helper that is not that opinionated and does not make many assumptions on how you architect you application.
Laravel and domain-driven design both are good in their own way, but they don’t get along very well unless you do some very un-Laravel-y things.
Good to see that there are people who try (and manage) to make it happen anyway. 😄
It's true it's not easy to use DDD in Laravel without rebuilding a lot of systems from the ground up. I'm tryring to find a middle ground here so we can use DDD & UML and bring some consistency to the hot mess Laravel apps tend to become after a few years 😅
Speaking of which, Laravel has native support for value objects in Eloquent models, check it out!
I think they get along pretty well. There is like a 5 minute process to add a domain folder that is autoloaded and you are pretty much ready to go. There are packages that helps you get even further very easily. Personally I really like github.com/lunarstorm/laravel-ddd - It's a very lightweight DDD helper that is not that opinionated and does not make many assumptions on how you architect you application.
That lib look dope.