Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • "uniqueness is a business constraint that's been mentioned several times by domain experts" - well, that just means that you should express it somehow within your domain model, it doesn't necessarily mean that you should implement every conceivable aspect of it. In other words, you can express the high-level behavior/policy in the domain model, but delegate details to the storage - there's a balance to be made there, of course, but after all, a db is nothing but a remote service you can ask questions of. Commented Jul 5, 2021 at 19:15
  • Thanks @FilipMilovanović, I completely agree, the technical implementation will live outside of the domain and domain will just define the interface to capture this requirement. My question is more about should this be in the InvoiceAR, Invoice Domain Service or treating the company AR and the invoice is a normal Aggregate and listed my worries with the second approach. Let me know if I can make my question more clear or if I missed your point. Commented Jul 5, 2021 at 19:19