Analysis of the popular J2EE WEB application architecture

Analysis of the popular J2EE WEB application architecture
--------------------------------------------------------------------------------
1. Architecture Overview
The J2EE system includes technologies such as java server pages (JSP), java SERVLET, enterprise bean, and WEB service. The emergence of these technologies provides a very competitive choice for the development of WEB applications in the e-commerce era. How to combine these technologies to form a stable architecture to meet the needs of the project is a very important step in the project development process. Completing this step forms a major milestone baseline. Creating this baseline has many benefits:
Preliminary Determination of various factors
To form an architecture baseline, architects should screen out technologies in the platform (system) and weigh the advantages and disadvantages. In this process, architects often need to read a large amount of technical materials, listen to suggestions from project team members, consider the needs of field experts, and consider the sponsor costs (including development costs and operation and maintenance costs. Once the architecture design is reviewed, these factors are initially positioned to play a significant role in the entire project process.
Targeted technical training
Once the architecture designed by the architect is approved to form a baseline, the technology used for project development and operation is basically determined. Many project managers are worried about the technical skills of the members of the preparatory project team. They need to provide training for the training department, but they are concerned about the technical Ocean faced by architects, the project manager cannot provide clear technical training requirements. How can we not train all technologies in the system! With the architecture milestone baseline, the project manager can determine the technology used in the project development. This is the most accurate requirement for training. However, in actual project development, technical training can be conducted with architecture design concurrency before baseline determination.
Role Division
With a good architecture blueprint, we can accurately divide our work. Such as webpage design, JSP tag processing, SERVLET design, session bean design, and various implementations. These tasks can be clearly marked in the architecture blueprint so that project team members can locate their tasks well. A good architecture blueprint can also standardize tasks and classify tasks into several categories. The workload and nature of tasks in the same category are the same or similar. This workload is estimated to have a very good foundation.
Operation and Maintenance
As mentioned above, each task has a better position in the architecture diagram. Anyone can use it to quickly familiarize themselves with the running status of the entire project and quickly locate the error point when an error occurs. In addition, with a clear architecture diagram, the project version management also has a good version tree trunk.
Scalability
The architecture is like the trunk of a towering tree. As long as the trunk is firmly rooted, the trunk is thick and longer, it is easy to add some leaves. Similarly, it is very fast and easy to add one or two business components in a stable and tested architecture.
Everyone knows these benefits and is dedicated to forming such a J2EE application architecture (like the MFC in windows ). This journey has gone through two major stages: