Explore core concepts of Domain Driven Design, its pros and cons, modeling techniques, and hexagonal architecture to transform complex business requirements into effective software solutions.

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

As was shown in the [previous lesson](https://www.educative.io/collection/page/4927079282376704/4708195672522752/5718229709750272), DDD uses tactical patterns to represent a model. Consider the situation in which we need to create an object that does not need identification, such as an amount with value and currency. Value objects are useful in such cases.

Before going further with the definition of value objects, it is worth looking at a common situation of the real world. This example, taken from Eric Evans book on DDD, describes what a value object is from the real-world perspective:

<p align=" center" style="font-style: italic;"> “When a child is drawing, he cares about the color of the marker he chooses, and he may care about the sharpness of the tip. But if there are two markers of the same color and shape, he probably won’t care which one he uses. If a marker is lost and replaced by another of the same color from a new pack, he can resume his work unconcerned about the switch.” </p>

# What is a value object? 
A **value object** is a representation of something that is involved in a business process. Unlike entities, value objects are defined through their attributes rather than an identifier. This means that value objects do not have an ID, and they are identifiable only by their set of attributes. Hence, these objects are immutable. Some common examples of value objects are `Address`, `emailAddress`, `Amount`, and so on. 


As was shown in the [previous lesson](https://www.educative.io/collection/page/4927079282376704/4708195672522752/5718229709750272), DDD uses tactical patterns to represent a model. Consider the situation in which we need to create an object that does not need identification, such as an amount with value and currency. Value objects are useful in such cases.

Before going further with the definition of value objects, it is worth looking at a common situation of the real world. This example, taken from Eric Evans book on DDD, describes what a value object is from the real-world perspective:

<p align=" center"> “When a child is drawing, he cares about the color of the marker he chooses, and he may care about the sharpness of the tip. But if there are two markers of the same color and shape, he probably won’t care which one he uses. If a marker is lost and replaced by another of the same color from a new pack, he can resume his work unconcerned about the switch.” </p>

# What is a value object? 
A **value object** is a representation of something that is involved in a business process. Unlike entities, value objects are defined through their attributes rather than an identifier. This means that value objects do not have an ID, and they are identifiable only by their set of attributes. Hence, these objects are immutable. Some common examples of value objects are `Address`, `emailAddress`, `Amount`, and so on. 


Learn what value objects are and how they are implemented in DDD.

Introduction

Mapping Domain to Model

Domain Activities

Domain Objects

Domain Abstractions

Hexagonal Architecture

Conclusion

Value Objects