Summary
Sometimes, software design experts get into confusion when to and when not to use domain models. The following points might help you get an insight into DDD for efficient decision making and decide to implement DDD or not:
- Business cases and requirements are particular, specific to domains, and not related to technology implementations
- As an independent team, they wanted to go to DDD when:
- The team has never done earlier that sort of business cases
- The team need help from domain experts
- The business cases are more complex
- The team need to start from ground zero, and there are no previous models exists
- When the given design problem is important to your business
- Skilled, motivated, and passionate team to execute
- Have greater access to domain experts who are aligned with product vision
- Willing to follow iterative methodology
- Nontrivial problem domain that is critical to business
- Great understanding of vision
- Business goals, values, success and failure factors, and how is it going to be different...
