Recently feel that their framework is too complex, in the implementation of the development of some uncomfortable, my friends often and I said that the framework is too cumbersome, to refer to the class library too many, the previous architecture was designed to be completely out of separation of duties and code reuse considerations, the main reference to Microsoft's DDD masterpiece "N_ Layerapp "This project, and in the years of project development, also tasted the sweetness of this responsibility-sharing framework, but in recent development, also saw the emergence of other frameworks, such as the ABP Project, which advocates simple framework, agile development, in the project reference on the core class library and persistence layer abstraction separation, Reuse in your field projects, this is the whole feeling of the project is more simple, and more easily accepted by people!
LIND.DDD Frame structure diagram
LIND.DDD Agile Domain Driver Framework Catalog
LIND.DDD Layer Introduction
Lind.DDD.Repositories.EF Layer Introduction
Lind.DDD.Repositories.Mongo Layer Introduction
Lind.DDD.Repositories.Redis Layer Introduction
Implementation of Lind.DDD.UoW working unit
Lind.DDD.Domain Domain Model Introduction
Lind.DDD.Events Field Event Introduction
Lind.DDD.Authorization User Authorization Introduction
Lind.DDD.Caching Distributed Data Set cache introduction
Introduction to Lind.DDD.Messaging Framework communication components
Lind.DDD.IoC Dependency Injection and aspect-oriented implementation
Lind.DDD.Paging Paging Module Introduction
Introduction to the Lind.DDD.Specification Statute model
Thank you for your attention ...
LIND.DDD Agile Domain Driven Framework ~ Introduction