Only use it if you have complexity to manage. The corollary to the above is the Domain Driven Design is overkill when working on simple domains or simple pieces of software.
#Eric evans domain driven design software#
![eric evans domain driven design eric evans domain driven design](https://res.cloudinary.com/value-object/image/upload/t_speaker19v2/v1541095170/dddeu19_site/eric_evans.jpg)
![eric evans domain driven design eric evans domain driven design](https://images-na.ssl-images-amazon.com/images/I/81Tx5LAzr8L.jpg)
The Domain Driven Design perspective is not reductionist, but rather embraces the notion that software development is part of a much larger and complex socio-technical system.
![eric evans domain driven design eric evans domain driven design](https://www.cdiscount.com/pdt2/2/1/7/1/550x550/auc9780321125217/rw/domain-driven-design-evans-eric.jpg)
The concept was introduced by Eric Evans, and the original textbook was published in 2003. What the interviewer expected to hear, was enthusiasm and eagerness to. A set of guiding principles that together form a mindset about building software, often abbreviated as DDD. And then in 2003, Eric Evans would not have needed 560 pages to write a book about it.