Can someone please clarify the following topic? I haven’t found enough complex answer to this, just some basic examples of how this should work, so I am asking here. Let’s say we have an entity Invoice. The Invoice has some private props like date issued, payment date, Items, etc. By the principle of DDD the Domain should care only about
Tag: domain-driven-design
DDD, problem with value objects and “new Domain()”
I have a question, I am migrating from MVC to hexagonal architecture and DDD architecture in a laravel project. I understand that a value object represents an attribute of table X but I have a problem, I have a table with 60 columns, would it have 60 value objects? That same table in the laravel controller has a join with
What should I test in an application layer service
I wrote the following application service for a project I’m working on, but struggled to write a good unit test for it. As you can see, the service itself doesn’t perform any meaningful logic other than orchestrating the domain layer (as it should if I understand correctly, according to the blue book). What would be your suggestions to unit test