![]() ![]() ![]() Developers will first face a steep learning curve and managing the architecture will make things longer to build. Going for a Domain-Driven approach also means higher costs at first. It is a good fit for dealing with highly complex domains, and projects beginning to dip into legacy. The goal of Domain-Driven Design is to free up the domain code from the technical details, to have more space to deal with its complexity. Other implementations and vocabulary also exist, as well as similar architectures sharing the same principles, such as clean architecture and hexagonal architecture. You’ll find in this article an introduction to Domain-Driven Design that mostly follows what is explained in Eric Evans’ book. In Domain-Driven Design, business logic is considered to be the heart of the software. In other words, the “Domain” is what is commonly referred to as “business logic” in the software world. “Domain” in Domain-Driven Design officially refers to a “ sphere of knowledge and activity around which the application logic revolves”. on Unsplashĭomain-Driven Design is an approach to software development based on making your software deeply reflect a real-world system or process.
0 Comments
Leave a Reply. |