CODEWITHSUNDEEP
architecturedomain-driven-designcomponentssoftware-design
Rasika Bandara
Rasika Bandara

Reputation: 93

Implementing component based design with DDD

I'm new to DDD but have some idea about it. I have plan to develop component base application with C#. First I have created ER diagram and with that I have created db schema.

I chose component like EmployeeManagement, ProjectManagement and ResourceAllocation. But both EmployeeManagement and ResourceAllocation components use Employees table and also ProjectManagement and ResourceAllocation components use Projects table.

I have separated DataAccessLayer files for each components to access dbContext. Is this a quality wise acceptable solution or is there any other ways to improve current design?

Upvotes: 0

Views: 724

Answers (1)

L-Four
L-Four

Reputation: 13551

First, your database design has nothing to do with DDD or how your domain model looks like.

If your question is about design patterns, probably the repository pattern is what you are looking for.

If you want to use DDD principles, start by designing a domain model (defining aggregates, entities, value objects etc) and don't think of databases or technical details.

Upvotes: 1

Related Questions