Author: Eric Evans

Domain-Driven Design appeared in 2003 and handed software teams a vocabulary they did not have: ubiquitous language, bounded context, aggregate, anti-corruption layer. The argument underneath is that the hard part of a large system is not the code but reaching agreement on what the business means by its own words. Evans had spent years consulting on projects big enough to fail in exactly that way. He runs a consultancy and a training business built on the book, which has outlived several generations of the technology it was written against.