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

This section will cover the benefits and drawbacks that people may come across when implementing DDD. These will lead to better trade-offs, resulting in the best outcome for companies and projects.

## Benefits of Domain Driven Design 
### Flexibility 
When a project is based on Domain Driven Design, it is easier to evolve and change things like business processes, implementations, or technological stack, which gives us a better time to market.
### Code is organized 
Domain Driven Design can work together with Hexagonal architecture. This concept is going to be covered in the coming lessons. Hexagonal architecture aims to organize the code of an application in a specific structure. It will help developers understand and modify code much easier when necessary.
### Business logic lives in one place
When organizing code based on hexagonal architecture, there is a layer where all business objects are placed. It allows for a team to change business logic easier because they should only concentrate on one layer. The yellow hexagon in the image below represents the logic defined by analyzing a business process. Once any business rule changes, it is easy to evolve code in this layer according to new business rules. The business logic code must not spread out other layers.

This section will cover the benefits and drawbacks that people may come across when implementing DDD. These will lead to better trade-offs, resulting in the best outcome for companies and projects.

# Benefits of Domain Driven Design 
## Flexibility 
When a project is based on Domain Driven Design, it is easier to evolve and change things like business processes, implementations, or technological stack, which gives us a better time to market.
## Code is organized 
Domain Driven Design can work together with Hexagonal architecture. This concept is going to be covered in the coming lessons. Hexagonal architecture aims to organize the code of an application in a specific structure. It will help developers understand and modify code much easier when necessary.
## Business logic lives in one place
When organizing code based on hexagonal architecture, there is a layer where all business objects are placed. It allows for a team to change business logic easier because they should only concentrate on one layer. The yellow hexagon in the image below represents the logic defined by analyzing a business process. Once any business rule changes, it is easy to evolve code in this layer according to new business rules. The business logic code must not spread out other layers.

Compare the benefits and drawbacks of Domain Driven Design in this lesson.

Introduction

Mapping Domain to Model

Domain Activities

Domain Objects

Domain Abstractions

Hexagonal Architecture

Benefits and Drawbacks of DDD

Benefits of Domain Driven Design

Flexibility

Code is organized