4 ms·

While skimming over the repo, I am seeing a couple of warnings that indicate leaking abstraction/boundaries : * there are imports for Spring in the domain code

While skimming over the repo, I am seeing a couple of warnings that indicate leaking abstraction/boundaries : * there are imports for Spring in the domain code (is Spring part of your domain?) * you are using a mock framework in some domain tests Also I am not sure I understand the "domain" and "ddd" packages. I am a huge supporter of splitting a "domain" package from a "application" package like you did, but then not sure where the ddd stands

tlandeka 4y ago
Q: there are imports for Spring in the domain code (is Spring part of your domain?) A: At only one place in order to be easy to replace it. I followed Vaugh Vernon example of mixing it: https://github.com/VaughnVernon/IDDD_Samples/blob/master/iddd_identityaccess/src/main/java/com/saasovation/identityaccess/domain/model/DomainRegistry.java https://github.com/VaughnVernon/IDDD_Samples/blob/master/idd... Q: You are using a mock framework in some domain tests A: Yes. Can you write some pros/cons regarding to this. "domain" is real domain that contains business logic, "ddd" should be extracted to a common library (according to this example https://github.com/VaughnVernon/IDDD_Samples/tree/master/iddd_common/src/main/java/com/saasovation/common https://github.com/VaughnVernon/IDDD_Samples/tree/master/idd... and this one https://github.com/dddshelf/ddd https://github.com/dddshelf/ddd)