Using Java-EE architecture enterprise Application

Enterprise-class applications are solutions and applications that are created and deployed for business organizations, large enterprises. The structure of these large enterprise applications is complex, involving many external resources, transaction-intensive, large amount of data, and many users, with strong security considerations.

Contemporary enterprise applications can never be a stand-alone system. In an enterprise, there are typically multiple enterprise-level applications that are interconnected, interacting across different tiers of integration, and are likely to be connected to other enterprise applications, thus constituting a complex, distributed enterprise application cluster spanning both the intranet and the Internet. Among them, the technology that connects various applications within Enterprise is called EAI (Enterprise application integration, enterprise application integration), and the technology that connects the various applications between enterprises is called B2BI (business-to-business Integration, enterprise integration, using EAI, B2BI technology and the previous N-tier architecture is the biggest feature of today's enterprise applications.

In addition, as an enterprise-class application, it should not only have a strong function, but also to meet the future business needs change, easy to upgrade and maintenance.

Enterprise-Class Application architecture

Here we use a diagram to simply parse the architecture of the enterprise application, as shown in Figure 1.

Figure 1 Architecture for enterprise-class applications

The main body of this architecture is the MVC architecture. MVC is the abbreviation for Model/view/control. Model/view/control is a typical structure of software design. In this design structure, an application is divided into three parts: Model, view and controller, each part is responsible for different functions. Model refers to the business data/information processing module, including the business data access, processing, integration, etc. view refers to the user interface, that is, user-oriented data representation, controller is responsible for the process control between view and model, That is to complete the two-direction action: 1. Map the user interface (View) operation to the specific model to complete the specific business logic; 2. The business data processed through model will be reflected in the user interface (View) in a timely manner.

The MVC architecture makes the structure of the application clearer and enhances code stability by dividing the code hierarchically into business logic/data, user interfaces, and application processes to control these three levels. We know that for model, view, controller these three functions, view is generally implemented by interface designers and interface programmers to complete, model is the business logic programmer to complete, controller is generally responsible for the overall control of the programmer to complete. The controller part of the code is more stable and generally implements a common architecture, while model follows the changes in the business process; View changes are changed as the user's requirements change. The partitioning of the module functions facilitates the isolation of modules in the process of code modification without the need to mix code with different functions to create confusion. In terms of project development, it is advantageous for the team members to work together according to their respective expertise, which is beneficial to three parts in parallel development and speed up the project progress.

Enterprise-level resource connectivity

For the model section, that is, the processing of business logic, the general business data is always processed, processed, integrated and so on. For enterprise-class applications, the Shang Mark  Ying Xin Street throw a bundle of  restore the sheath , duo  I restore a very small, Lu liling  na-guide Team tau Meng low field?lt;br>

This should be a familiar area for the database. We use SQL to query and manipulate the database by using a database driver. For other enterprise applications, these applications typically provide APIs that allow other applications to access the data in which they are accessed, or even to trigger some amateur processes in these enterprise applications.