Domain Driven Design Vs Mvc
Domain driven design concentrates on modeling and solving the domain problem by capturing the model from the ubiquitous language.
Domain driven design vs mvc. It is about modeling a domain of knowledge with a high level of abstraction and its focuses are on domain logic and tries to keep the design as much close to the real world. Domain driven design vs database driven design for an mvc web application. Robert harvey sep 9 16 at 14 56.
Asked jun 9 15 at 19 20. Domain driven design ddd advocates modeling based on the reality of business as relevant to your use cases. It describes independent problem areas as bounded contexts each bounded context correlates to a microservice and emphasizes a common language to talk about.
However moving from a database driven design to domain driven design seems to inversely impact the performance requirement if i compare it to the performance of the legacy dbdd application. 683 1 1 gold badge 7 7 silver badges 19 19 bronze badges. Mvc is more.
Domain driven design provides a set of principles and patterns that are useful for tackling complex software problems. According to eric evans domain driven design ddd is not a technology or a methodology. In the context of building applications ddd talks about problems as domains.
In the legacy application any call. Share improve this question follow edited jul 22 15 at 19 18. Common architecture with domain driven design model is presented on the right side of the picture.
The domain model provides a structural view of the system. Take note of a layer of services which is much thinner than his equivalent in an anemic model. Ask question asked 8 years 5 months ago.