A little understanding of spring's design goal
In the application development, faced with two fields:
1, the business domain
2, the computer domain
Want to do is to understand the business domain of the process, how to the mathematical model is set up in the computer field,
In the process of modeling, both must consider the requirements of the business domain, in order to design appropriate data structures and algorithms
To describe business processes, and at the same time, also want to consider the requirements of the computer domain, in the design of the business domain
Data into the computer domain data related to management in the operation process, etc., which leads to
Computer domain data into the business domain, the development, testing, deployment is adverse, for example,
Using the Java ee framework development and application, define an EJB, we need to inherit and achieve a lot of abstract classes and interfaces,
Spring framework proposed by two points, very good to solve the above problem:
1, the use of POJO development enterprise applications,
2, the program to an interface,
First of all, using pojos to develop, such, can only consider the business domain related data, as for
To manage data, provided by the spring framework, need not consider,
The second point, makes the business logic in the design, it is good to consider only the required functionality, as to the specific implementation of function,
Shall be available on demand, arbitrary switching, corresponding dependence and assembly, to the spring framework to implement (IoC and AOP),
So, can consider business from a higher level of implementation, convenient for application development, testing, deployment, etc.,
CodePudding user response:
Point a,,,CodePudding user response:
