Infrastructure layer to provide underlying functions for the System

Infrastructure is to provide specific technical support for the system. The data persistence layer (DAL) is also a type of infrastructure layer, but the data persistence layer is generallyCodeBecause the quantity and the number of classes are large, we will propose them separately. The rest will be mentioned in another infrastructure layer.

In addition to the Dal, what else do we need to put in the infrastructure? For example, an object is used to generate a word report, and messages in the system are sent to the specified email address as email.

In essence, the infrastructure is the same as the data persistence layer. Generally, there is little business project that has business or stores various statuses. Basically, they are all independent functions to complete specific underlying functions, which will be organized at the appservice layer to complete specific business functions.

In fact, it is difficult to distinguish between the domain layer and the infrastructure layer. For example, when creating a system related to arcengine, an object has spatial information. The spatial information indicates that the object is an ifeature object, but the ifeature is an interface in arcengine, it seems that ifeature is an object related to the specific implementation technology, but if the object does not store ifeature, where should the object be stored?

Our system is built on arcengine, and the entire system is closely integrated with arcengine. It is difficult to simply separate it from each other. Therefore, ifeature should be placed in the domain object.