When We Should Use Domain Driven Design Approachby@mrr

When We Should Use Domain Driven Design Approach

tldt arrow
Read on Terminal Reader

Too Long; Didn't Read

Domain Driven Design(DDD) is an alternative for our previous approach in three-layer design. DDD wants to change the focus of the programing from storing and retrieving information to a layer called Domain. The Domain layer often comes into play for the Create, Update and Delete operations (which change the state of the system) and usually does not provide any special added value in the Read and querying data. This attitude has its costs and benefits in software development and is not going to magically solve all our problems.

Company Mentioned

Mention Thumbnail
featured image - When We Should Use Domain Driven Design Approach
Mohammad Reza Rahimi HackerNoon profile picture

@mrr

Mohammad Reza Rahimi

About @mrr
LEARN MORE ABOUT @MRR'S EXPERTISE AND PLACE ON THE INTERNET.
react to story with heart
Mohammad Reza Rahimi HackerNoon profile picture
by Mohammad Reza Rahimi @mrr.I am a Full-Stack .Net Developer with more than 10 years of experience.
Read My Stories

RELATED STORIES

L O A D I N G
. . . comments & more!
Hackernoon hq - po box 2206, edwards, colorado 81632, usa