Domain Driven Design or DDD for short is a huge but interesting topic. It has many complex subjects focused on business and technical perspectives. In the technology industry, people always talk about how both perspectives should work together in order to give the business benefits. However, that is not an easy task and it is when DDD appears in the scene. In this course, you are going to learn the most important concepts of DDD. You will see some concerns, techniques to model, how DDD can be implemented using hexagonal architecture and many other amazing concepts.

Domain Driven Design (DDD) Made Easy

Once a team has defined its bounded contexts, modules, or microservices, the team is going to implement interactions between them. It is time to think of how those interactions have to occur.

Purity is all about maintaining a model away from something that may mess up the model, for example, models of external applications, databases, legacy systems, and even models of other bounded contexts.

Let us imagine there is a component called **Transfers** that needs to obtain information from a third-party application. This external application does not follow the model of Transfers created by the DDD team. In this case, it would be necessary to create a coupling between Transfers and the external service. It is crucial to avoid some type of coupling.

# What is an anti-corruption layer?
The anti-corruption layer (ACL) is a strategic pattern in the DDD world. It is nothing but a translator that translates a bounded context model into an external model and vice versa. One of the most important things when implementing components based on Domain Driven Design is to avoid corrupting business logic in any way. Once core business logic is implemented, it will need to interact with external components. It is impossible to implement any external connection from the domain logic. To achieve it, the anti-corruption layer exists, which can be implemented by using some design patterns such as **Facade**, **Adapter**, or even by coding a custom translation.

Learn how to maintain the purity of the bounded context by implementing an anti-corruption layer.

Introduction

Mapping Domain to Model

Domain Activities

Domain Objects

Domain Abstractions

Hexagonal Architecture

Maintaining Purity