In this course, you are going to learn the most important concepts of Domain Driven Design or DDD for short. You will see both benefits and drawbacks, techniques to model, how DDD can be implemented using hexagonal architecture and many other amazing concepts.

By the end of this course, you will be able to take complex business requirements and processes and turn them into meaningful software.

Domain Driven Design Made Easy

Make attributes `final` so they are immutable.

Guarantee that there is an identifier for the objects.

If it is necessary to maintain some type of state, what should be the best approach to tackle it?

If it is necessary to maintain some type of state, what should be the best approach to tackle it?

What will be the best approach to take when logic does not fit into any entity or value object?

What will be the best approach to take when logic does not fit into any entity or value object?

A domain service should have stateless business logic.

A domain service should have stateless business logic.

A domain service is the best place to put the database connection logic.

A domain service is the best place to put the database connection logic.

A repository is the best place to put an email-sender logic.

A repository is the best place to put an email-sender logic.

Define a repository that connects with several storage systems.

Define a service that handles the creation of all objects.

Define a factory that handles the creation of all objects.

If it is necessary to create an object that depends on many other objects, what is the best approach to do this?

If it is necessary to create an object that depends on many other objects, what is the best approach to do this?

Introduction

Mapping Domain to Model

Domain Activities

Domain Objects

Domain Abstractions

Hexagonal Architecture

Conclusion

Quiz