This architecture is often confused with DDD, reducing DDD to a modeling concept, ignoring its architecture. The four-tier architecture, which consists of a user interface (UI) tier, business tier, data access tier, and database tier, uses database technologies and Model-View-Controller (MVC). This model has been widely used in actual applications and promoted by the use of popular object-relational mapping (ORM) frameworks such as Hibernate and Entity Framework. For example, Martin Fowler described an anti-pattern called anemic domain model in his blog. This makes it difficult to apply DDD to actual software development and causes a great deal of misunderstanding about DDD. Prefaceĭomain-driven design (DDD) is an architectural concept rather than an architecture, so it lacks sufficient constraints for coding.
A complete set of architecture concepts for business development are proposed in some other books, such as Domain-Driven Design by Eric Evans in 2003, Implementing DDD by Vaughn Vernon, and Clean Architecture by Uncle Bob. However, they leave business problems unsolved. These books propose the concept of solving technical problems by technical means. A series of books, such as Design Patterns: Elements of Reusable Object-Oriented Software by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides in 1994, Refactoring by Martin Fowler in 1999, Patterns of Enterprise Application Architecture in 2002, and Enterprise Integration Patterns in 2003 Plethora, advocates the practice of minimizing system complexity through design patterns or paradigms. Every architect strives to minimize system complexity in software development.
0 kommentar(er)
