Change Tracking while doing DDD

Guide on implementing Change Tracking while having separate Domain & Persistence Models in .NET Core

The most important thing to keep in mind while doing DDD (Domain Driven Design) is to focus on business domain problems, and model the domain so it reflect the ubiquitous language spoken by domain experts. It is true that we inherently should not worry about the persistence mechanism, because rightfully so, it is an implementation detail that the domain should not need to worry about.

Yet what is a software worth if it doesn’t … well “implement” things? I would say just as good as your white paper concept.

To read more on this topic, please visit my blog.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store