Domain driven design vs event driven design

#Domain driven design vs event driven design software#

The business logic of an application refers to the higher-level rules for how business objects (see: OOAD) interact with one another to create and modify modelled data.

#Domain driven design vs event driven design software#

In other words, during application development, the domain is the вЂњsphere of knowledge and activity around which the application logic revolves.вЂќДЄnother common term used during software development is the domain layer or domain logic, which may be better known to many developers as the business logic. The common dictionary definition of domain is: вЂњA sphere of knowledge or activity.вЂќ Drilling down a bit from that, domain in the realm of software engineering commonly refers to the subject area on which the application is intended to apply. To define domain-driven design we should first establish what we mean by domain in this context (and in development in general). Throughout this article weвЂ™ll examine what domain-driven design is, how it is commonly implemented in modern development life cycles, and consider a few potential advantages and disadvantages of using DDD in your own projects.

DDD is a software development approach that uses and builds upon OOADprinciples and ideas, so itвЂ™s the next logical topic for us to dive into. Expanding on our previous article that covered Object-Oriented Analysis and Design ( OOAD), todayвЂ™s article will explore domain-driven design ( DDD).