Technicians are often troubled by selection problems, especially the application system framework. I believe that many people have wandered between lightweight and heavyweight frameworks for a long time, but have been unable to make up their minds.
Albert Einstein once said: "Everything should be as simple as possible, but not simpler".
Simple is beautiful. Obviously, I personally prefer lightweight frameworks.
In the context of Java application development, "lightweight Java" primarily refers to two things: a simplified programming model and a more responsive container, according to Jim Rivera, director of technology at BEA. Lightweight J2EE frameworks are designed to remove the unnecessary complexity and limitations associated with traditional APIs, reducing application deployment time. Also, it does not force business objects to conform to platform specific interfaces. This allows developers to implement business logic in plain POJOs, increasing productivity.
Of course, lightweight frameworks have difficult problems to solve, which is what WebLogic, WebServer, etc. are good at: distributed transaction processing and other advanced features are the qualities of high-end application servers.
Another difference between the two is reflected in development costs and operating costs.
With the rapid development of information technology, XP enables developers to more effectively respond to changes in customers' needs, and is thus widely popular. The emphasis on development costs has also reached an unprecedented level, and the development of lightweight frameworks has also taken off. Products such as Spring, jQuery, Velocity, and Nginx have gained a broad market and have a significant presence in the technology space.
Many people believe that lightweight frameworks are only suitable for developing small and medium business applications, and may not be a performance issue. Through clustering and load balancing technology, lightweight frameworks are also capable of high-concurrency applications.
We don't have to hesitate too much on this issue.