In order to address the challenges of WTO and fierce market competition, the company's informationization is getting deeper. In the initial stage of informationization in the company, it is based on business, the most important thing for application software is to meet current business needs. Over time, the degree of informationization is deepened, and the contradiction between enterprises informatization is increasingly prominent. Here: 1. Flexibility: Due to various reasons such as changes in the internal and external environments, the demand of information is constantly changing, which requires the application system to flexibly adapt to various changes in demand, that is, the response. Unfortunately, we often see that the application system needs to be "injured and hurt the bones" due to changes in demand. 2, openness: Interconnect interconnection between different application systems within the enterprise is a problem that plagues the company. 3. Reusability: Between different applications, there are many common functions, such as organizational architecture, permission control, etc. Extraction of these commonly extracted will greatly improve the development efficiency and flexibility. The currently popular SOA (Service-Oriented Architecture) architecture and ESB (Enterprise Service Bus) are intended to overcome the above contradictions. Its core thinking is that an application should be divided into loosely coupled, coarse-grained services, and coordinated between a service bus service between a service bus. However, what should the service use as a carrier? It should be said that according to specific situations, services can have different carriers: COM, CORBA, EJB, Web Service, thread, etc., but the most important carrier is a process. This is because the process has the lowest coupling degree, and has the broadest support, thus the most conforming to the idea of service in the SOA architecture, and when the process is used as a service carrier, the implementation of this process can be used in different operating systems, different The programming language is implemented, that is, the service implementation is independent of the operating system and programming language, so that the service can be implemented in the most suitable programming language, and the risk of prior art is eliminated. Each service carrier has its corresponding service bus, and the process service bus corresponding to the process service has the greatest inclusion and versatility, not only provides communication, but also provides communication between other service bus, making any service The carrier can communicate on the process service bus, as shown in the following figure. The role of the process service bus and the role of TCP / IP are very similar, and TCP / IP can accommodate other communication protocols in addition to end-to-end communication. Thus, all applications of enterprises should be based on service, although different services may have different service bus, but finally, they are unified to a universal process service bus. In summary, process service bus and process services are the most core idea of enterprise application platforms. The essential idea of XML is to separate the description and processing of things. As described as much as possible, it not only brings great flexibility, but also allows us to quickly respond to changes in demand. However, when describing more and more, we need to introduce object-oriented ideas between descriptions, just like C to C evolution. The application of the B / S architecture is increasing, but its development mode is more primary, and there is a large number of commonality between the pages, making larger B / S applications are very flexible, if the web page is effective Description, and generate web pages based on the idea of objectualization, the web application will make web applications that have great flexibility and reusability. Objectualization Description should be another core idea of the enterprise application platform. In summary, process services and objective descriptions are two most important core ideas that build a architecture most flexible, reusable, and effectively eliminate "information islands" enterprise development platform.
