A developer who can tactically support simple architecture influenced by Domain-Driven Design.
- Discuss 3 goals of DDD in regards to a software project
- Defend the utility of an ubiquitous language on both the business and tech side
- Structure a code project in a way that correctly separates domain code from application code
- Implement the Repository Pattern to abstract database code from consumers
- Implement services to encapsulate business logis
- Write code that utilizes dependencies that have been properly "injected"
- Describe the purpose and meaning of entities
- Create entities that work seamlessly with the ORM
- Defend the need for code-first database design over database-first design
- Domain-Driven Design Crash Course{:target="_blank"}
- Introduction to DDD Lite{:target="_blank"}
- Repository Pattern{:target="_blank"}
- Domain-Driven Design: File Structure{:target="_blank"}
- Words Matter: Ubiquitous Language and Throughput{:target="_blank"}
- Code-First vs Model-First vs Database-First: Pros and Cons{:target="_blank"}
Ask your mentor if you are ready for evaluation. Then, do one of the following:
- Schedule a live evaluation by clicking here to find a time on the calendar. After the evaluation, claim the badge.
or
- Record a screencast where you talk about and demonstrate each competency listed above. Make sure badge criteria and relevant tools are visible in the screen cast AND that your audio is good enough for the evaluator to hear. Upload the video to a service like Vimeo or Youtube (unlisted is fine) so that you can provide a public url for an evaluator to view. Claim the badge and include the video url in the evidence box.