An introduction to DDD - Rob Allen

How are you supposed to organise your models in an MVC application? What goes where? What is a service class, a mapper or an entity? Domain Driven Design focusses on modelling the domain logic and helps us to map the business requirements to our software. We'll discuss the terminology and take a look at what Domain Driven Design is and see how you use it to provide the model logic for your application decoupling it from your controllers. By the end of this session you will be equipped to create excellent, maintainable models in your application.

[@DevflowCMF]

This is a talk that one can listen to over and over and continue to learn something new every time. Love it!

[@igorpronin9484]

Good talk. Very inspiring.

[@ThomasPraxl]

Regarding the question: "Is it advisable to use native language in the code, e.g. for class names": It feels strange at first, but it is advisable unless you manage to change the commonly spoken language, which is rather unlikely to happen. The whole Ubiquituous Language idea comes down to not being forced to "translate" between the language (or mental model) actively used by domain experts and the language used by development team. And there are rare cases of unambiguous translation alternatives. Once you translate the actively used language to English, you will encounter wrong translations, different terms for the same thing, and confusion in discussions. I would therefore recommend using the native language. Give it at least a try.