SSM framework overview

  Framework is the reusable design of the whole or part of the system, which is represented as a set of abstract components and methods of interaction between component instances; another definition believes that a framework is an application skeleton that can be customized by application developers. The former is from the application side and the latter is the definition given from the purpose side.

  In short, a framework is actually a semi-finished product of a certain application, a set of components for you to choose to complete your own system. Simply put, you use the stage set up by others and you do the performance. Moreover, the framework is generally mature and constantly upgraded software.

  The most important problem to be solved by the framework is the problem of technology integration. In the J2EE framework, there are a variety of technologies. Different software companies need to choose different technologies from J2EE, which makes the final application of software companies. Relying on these technologies, the complexity of the technology itself and the risks of the technology will directly impact the application. The application is the core of a software enterprise and the key to competitiveness. Therefore, the application's own design and specific implementation technology should be decoupled. In this way, the research and development of software companies will focus on the design of the application, rather than the specific technical implementation. The technical implementation is the underlying support of the application and it should not directly affect the application.

1. The importance of stratification

  The importance of the framework is that it implements part of the functions, and can well ease the low-level application platform and high-level business logic. In order to realize the "high cohesion and low coupling" in software engineering. Dividing the problems into individual solutions is easy to control, easy to extend, and easy to allocate resources. Our common MVC software design idea is a good layered idea.

Insert picture description here

  The responsibilities of each part are better realized through layering, and different frameworks will be refined at each layer to solve the problems of each layer.

2. Common frameworks under layered development

  • Mybatis, a framework to solve the problem of data persistence:

  MyBatis was originally an open source project iBatis of apache. In 2010, this project was migrated from apache softwarefoundation to google code and was renamed MyBatis. Migrated to Github in November 2013. The term iBATIS comes from the combination of "internet and "abatis" and is a Java-based persistence framework. The persistence framework provided by iBATIS includes SQLMaps and Data Access Objects (DAOs).

  As a framework for the persistence layer, there is also a framework with a higher degree of encapsulation, which is Hibernate. However, due to various reasons, the popularity of this framework in the country has dropped too much, and the company's development is now less and less used. Currently using Spring Data to achieve data persistence is also a trend.

  • SpringMVC, an MVC framework that solves the problem of the WEB layer:

Spring MVC is a follow-up product of SpringFrameWork and has been integrated into Spring Web Flow. The Spring framework provides a full-featured MVC module for building Web applications. Use Spring's pluggable MVC architecture, so when using Spring for WEB development, you can choose to use Spring's SpringMVC framework or integrate other MVC development frameworks, such as Struts1 (generally not used now), Struts2, etc.

  • Framework Spring to solve the problem of technology integration:

  The Spring framework was created due to the complexity of software development. Spring uses basic JavaBeans to accomplish things that could only be done by EJB before. However, the use of Spring is not limited to server-side development. From the perspective of simplicity, testability, and loose coupling, most Java applications can benefit from Spring.

  Purpose: To solve the complexity of enterprise application development.
  Function: Use basic JavaBean instead of EJB, and provide more enterprise application functions.
  Scope: Any Java application.

  Spring is a lightweight inversion of control (loC) and aspect-oriented (AOP) container framework.

Guess you like

Origin blog.csdn.net/Tracycoder/article/details/113662489