4 ms·
Let’s not confuse domain-driven design with data driven design. Most architects would assign the DDD acronym to Domain-Driven Design. </pedantic-rant>
by ChicagoDave 3y ago
Let’s not confuse domain-driven design with data driven design.
Most architects would assign the DDD acronym to Domain-Driven Design.
</pedantic-rant>
- reactordev 3y agoI align with this. Data driven design is an easier way to say domain driven design. They mean the same thing but because of the former, it’s confusing. DDD ensures you know the domain you’re working with, in language that the business is familiar with. A banking DDD would have Accounts Deposits Withdraws Authorized Users Statements etc.
- ChicagoDave 3y agoThey absolutely do not mean the same thing. Data DD - Account.Insert or - Account.Create Domain DD - Account.Open The former is a data store activity and the latter is a business activity.
- jbluepolarbear 3y agoDepends on the field, in real-time application and games it’s gonna mostly refer to data driven design more than domain driven design. Honestly haven’t heard domain driven design inside the games field since the early 2010s.
- rafaelmn 3y agoIs software architect a common title in game dev ? It's been a decade since I've looked at the field but it kind of antithetical to the industry as I remember it.
- eliasmacpherson 3y agoIt's been a long time since I've interacted with a software architect. As poor as wikipedia is a source for a layman like myself, I still use it as a first step to explore topics I am not familiar with. Would software architects be aware of all the various paradigms applicable within a particular language? Much like me trying to pick the right tool to complete a particular project... https://en.wikipedia.org/wiki/Programming_paradigm https://en.wikipedia.org/wiki/Programming_paradigm is there a good reason why Domain-Driven Design is not linked in the article above, or just an oversight? https://en.wikipedia.org/wiki/Domain-driven_design https://en.wikipedia.org/wiki/Domain-driven_design
- layer8 3y agoDDD is not a programming paradigm, it’s a software design approach. You can combine DDD with various programming paradigms such as OOP and FP.
- dragonwriter 3y agosoftware design approaches are frequently closely tied to programming paradigms, and DDD (while, like Object Oriented Analysis and Design, it can be used with any paradigm) is closely associated with OOP, and at least the early writing on it (if there is any newer that this isn't true of, I haven't seen it) is very tightly coupled with OOP.
- layer8 3y agoThat is true to a certain extent, but that doesn’t make it a programming paradigm.
- dragonwriter 3y agoYes, it was a related observation, not a refutation.
- eliasmacpherson 3y agoThanks for the clarification. So just to spell it out: Domain-driven design (nor Data-driven development per the article title, nor Data-driven design) aren't programming paradigms, they are software design approaches. Whereas Data-driven programming, as linked from the above wikipedia is infact a paradigm and something else entirely. Alright. They have 'Data-oriented' listed in the wikipedia paradigm article, but it links to 'Data-oriented design' which is clarified as a software design paradigm, as distinct from a programming paradigm.