Domain Driven Design - Clear Your Concepts Before You Start ✨

What we traditionally do when we start a business application❓

We read the spec and find the functionalities. We break down tasks. ✅

We do the estimation. We distribute the works among team members. We design the database schema - sometimes by the team leader or sometimes by the respective developer. We start coding. 💻

So❓ What’s wrong with this approach❓We have been doing good❗️Don’t we❓

The answer is YES and NO❗️Yes we are doing good in delivering our projects. But NO❗️
We are not doing good in maintaining and extending our projects. 🤦🏻‍♂️

Think about all of the projects you have worked last few years in the traditional approach. Did you ever face any of the issues below ? 🤔

Your project has the same functionality implemented in the same way or different in different places. 👥

You have more than one object for the same item. ❌

You have objects that have properties that are not actually attributes of that object. 🙅🏻‍♂️

You have no or very poor relationship among related items. ↔️

Looking at your objects it is not possible to understand what actually the whole application is all about. 🤷🏻‍♂️


https://t.me/pgimg/184

[ Article ] : kutt.it/ddda

〰️〰️〰️〰️〰️〰️
#DDD #Architecture
@ProgrammingTip