atsapura / cardmanagement Goto Github PK

Not really an issue, but there wasn't a discussion forum or I'd have put it there.

I've been reading through your (fantastic) article, I think you bring up a lot of really great ideas.

Curious if you'd be willing to expand on your opinion where the contract mapping code lives in the Domain project.

Normally I've been keeping the contract code purely to the boundaries of the application. My thoughts are that it is the concern of the WebAPI layer to define/maintain the definitions of how the domain aggregates are represented to other systems. Similar to how you've done it in the Data layer. The Data layer is concerned with the representation/mapping of the domain to however it looks when persisted to the database.

Would you argue that the definition of the exposed contract is the concern of the domain? I'm not trying to push one way or the other, just interested in hearing you expand on your thoughts..

Link is broken at the moment