# Introduction Domain Driven Design (DDD) is an architectural approach first outlined by Eric Evans. With DDD, you focus first on developing a deep understanding the business. By collaborating with business stakeholders and subject matter experts we are are able to identify the different [[2. Domains & Boundaries|domains]] within the business. The [[Ubiquitous Language|unique language]] teams use is explored, documented, and deeply incorporated into the software being developed. Logical separations between different parts of the business are revealed through collaboration with subject matter experts. By focusing on how business leaders and subject matter experts understand how the business works, we can deliver a product that directly mirrors the business right down to the jargon the team uses. If we have done DDD right, our code will be a representation of how the business actually works. Any changes to the business requirements, can be achieved by making identical changes in the code. They are one you see, the business and the code. # Microservices Domain Driven Design is a concept that predates the [[microservices]] craze of today, but the two approaches are well-suited to one another.