[{"data":1,"prerenderedAt":72},["ShallowReactive",2],{"term-d\u002Fddd":3,"related-d\u002Fddd":59},{"id":4,"title":5,"acronym":5,"body":6,"category":39,"description":40,"difficulty":41,"extension":42,"letter":43,"meta":44,"navigation":45,"path":46,"related":47,"seo":52,"sitemap":53,"stem":56,"subcategory":57,"__hash__":58},"terms\u002Fterms\u002Fd\u002Fddd.md","DDD",{"type":7,"value":8,"toc":32},"minimark",[9,14,18,22,25,29],[10,11,13],"h2",{"id":12},"eli5-the-vibe-check","ELI5 — The Vibe Check",[15,16,17],"p",{},"DDD is the abbreviation for Domain-Driven Design — the practice of making your code speak fluent Business. Your classes and functions should sound like what the business actually does, not like a computer science textbook.",[10,19,21],{"id":20},"real-talk","Real Talk",[15,23,24],{},"Domain-Driven Design — see Domain-Driven Design entry. The abbreviation DDD is universally used in architectural discussions. Core tactical patterns include Entities (identity-based), Value Objects (equality-based), Aggregates (consistency boundaries), Repositories, and Domain Services.",[10,26,28],{"id":27},"when-youll-hear-this","When You'll Hear This",[15,30,31],{},"\"Are you using DDD for this project?\" \u002F \"DDD is overkill for a simple CRUD app.\"",{"title":33,"searchDepth":34,"depth":34,"links":35},"",2,[36,37,38],{"id":12,"depth":34,"text":13},{"id":20,"depth":34,"text":21},{"id":27,"depth":34,"text":28},"architecture","DDD is the abbreviation for Domain-Driven Design — the practice of making your code speak fluent Business.","advanced","md","d",{},true,"\u002Fterms\u002Fd\u002Fddd",[48,49,50,51],"Domain-Driven Design","Clean Architecture","CQRS","Event Sourcing",{"title":5,"description":40},{"changefreq":54,"priority":55},"weekly",0.7,"terms\u002Fd\u002Fddd",null,"z_nTX9uCipL_ZopJchN5tLQUu-CWhe-DWma23QiYii4",[60,63,66,69],{"title":49,"path":61,"acronym":57,"category":39,"difficulty":41,"description":62},"\u002Fterms\u002Fc\u002Fclean-architecture","Clean Architecture is like an onion with strict rules: the inner layers (your core business logic) have absolutely no idea the outer layers (databases, API...",{"title":50,"path":64,"acronym":57,"category":39,"difficulty":41,"description":65},"\u002Fterms\u002Fc\u002Fcqrs","CQRS says: the way you write data and the way you read data should be separate systems. Writing (commands) goes to one model optimized for transactions.",{"title":48,"path":67,"acronym":5,"category":39,"difficulty":41,"description":68},"\u002Fterms\u002Fd\u002Fdomain-driven-design","DDD says your code should speak the same language as the business.",{"title":51,"path":70,"acronym":57,"category":39,"difficulty":41,"description":71},"\u002Fterms\u002Fe\u002Fevent-sourcing","Instead of storing 'balance: $100', event sourcing stores 'deposited $200, withdrew $50, withdrew $50'.",1776518271538]