This is a really great article, and totally the way DDD should be understood and advocated.
However, it was not the way I approached it. I was looking for patterns (e.g. Respository, Aggregate, etc.) to cure all my ills. Needless to say my DDD adventure was quite misguided. I persisted and eventually came to a proper understanding that the specific patterns and their example implementations were incidental. Some of them would likely not be needed or take different forms in different architectures. But the core methodology is still quite powerful, and continues to become even more applicable as time goes on.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a really great article, and totally the way DDD should be understood and advocated.
However, it was not the way I approached it. I was looking for patterns (e.g. Respository, Aggregate, etc.) to cure all my ills. Needless to say my DDD adventure was quite misguided. I persisted and eventually came to a proper understanding that the specific patterns and their example implementations were incidental. Some of them would likely not be needed or take different forms in different architectures. But the core methodology is still quite powerful, and continues to become even more applicable as time goes on.