Member-only story
Practicing Domain-Driven Design in C#
Key strategic and tactical considerations to take when building a new product with the domain-driven design concepts in mind
I have just finished reading Learning Domain-Driven Design by Vlad Khononov. It’s quite a short book (c. 300 pages) aiming to teach beginners all about domain-driven design.
I wanted to check I understood the concepts in the book by trying to put them into practise. I hope you will learn something by reading this too! This is how I got on…
What is Domain-Driven Design?
The idea of domain-driven design is to use the business requirements you are building for as the basis for your architecture.
The business team that is asking you to build the product are the ‘domain experts’ and the area of business they work in is the ‘domain’.
There is a lot of talk of using a ‘ubiquitous language’, which means rather than using coding words that non-techies might not understand, you name your classes, methods and variables and discuss stuff using words that would be used by the business team to describe the product.
