From the "Black Cave" of IT, I recently participated in the high-level annual meeting of IT. I have talked about IT's black hole in the event of many sociologists, financial experts and IT people. People think that IT seems to have become an obstacle to the development of industry, and even social progress. IT 'ugly surface' compensation: IT department, real cost center IT is from supporting business, booting business to restrict business development 80% -90% IT budget and IT human resources are spent on maintaining the old system The launch of the new business is required for months, and even the year, can't keep the customer's needs and market reactions IT really become a chicken rib? Can we discard IT? I think the reason is very simple, IT and business are actually a pair of developed contradictions, interdependent, promotion and balance: interdependent. Now, no one will suspect that the business is inseparable from IT. If there is no IT, any financial, telecommunications, government affairs and manufacturing business will be paralyzed; if there is no business needs, IT will also lose the value of existence and development. Mutual promotion. The development of business requires IT constantly innovation, such as the needs of various industries to the newspapers in different land trading (adoption exchanges, warranty payments), bringing the development of newspapers; and the innovation of IT also brings new business models The development of the Internet has no doubt, driving online banking, online securities, online insurance, driving the online business hall of Telecom, even directly affecting the online business travel of our clothing and food, shopping, online mall, has brought a lot of new Business model. Mutual balance. Since the business and IT is a pair of contradictions, then any party's lag or advance will bring another "uneasy", which will be integrated into contradictions, which will involve the break and reconstruction of existing balance. Therefore, what we see is actually how to develop IT, not those who are sensible, do not need IT problems. It is the continued existence of this contradiction, and IT will have sustainable development soil. Traditional development or integration, brought complex tradition, IT realization has no external custom development project or professional integration project. That is to develop, integration is integrated for development. When it is designed to develop projects, integrators and developers are determined as needed. Then select the relevant development platform, such as servers, databases, application servers, development tools, etc. Different applications are also available in different development projects, and different development platforms are used. This brings more development, the more difficult it is in the future. In a professional integration project, due to large enterprises must enter business data interaction with one or more data sources, some data sources may be other applications. In other words, the application cannot be developed without integration. Application integration will contain certain application development tasks, such as development and assembly components, connect them to backend systems, implement process flow and workflow, develop user interface, and test and debugging. And if only the existing systems in the integrated project, select an integrator, use a dedicated integrated server, such as a portal integration server or an information integration server or an application integration server, because it is far from The elbows will be stretched for the re-development required for new business processes during the integrated process. Traditional three most common application integration methods are point-to-point integration, enterprise messaging bus or middleware integration (EAI), is not very ideal for business process, main problems are: messaging bus and application Custom or proprietary integration. EAI and business-based integration have reduced the number of integration points compared to equal methods. However, both methods need to be customized or proprietary integration between messaging bus and per application, and different proprietary data formats are required at each integration point. Tight coupling between messaging bus and applications. All applications need to know the internal work mechanisms of other applications integrated with them. The integration between the system is granularized and has a tight coupling relationship with the message type.
Traditional EAI implementation The business process management (BPM) tool is proprietary. This hinders the application of other excellent standard products. Programming rather than abstract data access. Most of the data access, integration, and conversion work (enterprise information integration) have left the developer to accomplish manual coding. There are multiple different data sources in the enterprise IT environment. Developers must have different adapters to access these data sources, there is a conversion engine to redefine the data format, and data replication is required to implement physical integration of data. To achieve the integration of data sources, developers need to use the above tools to write integration requirements to the app. Although the above methods are feasible, this is neither efficient and lack of flexibility. So, when using isolated vision, the contradiction is heavy. In fact, development and integration is already a pair of contradictions. Any custom-developed application requires access to other applications, but also needs to be accessed by other applications, so the development is inseparable; and any integration is also for new applications, of course there will be new business processes. Development, so integration also inseparable from development. Conclusion is simple, if it is independently considering application development and application integration is worthless. Moreover, traditional application development and integration methods are not flexible enough, failed to standard. Therefore, the traditional method cannot construct an agile enterprise IT environment capable of meeting the needs of dynamic enterprises. SOA integration development and integration, the three traditional application integration methods are very complicated, expensive, and is not flexible. These integrated methods are difficult to quickly adapt to demand for the continuous production of changes in corporate modern business. Application development and integration based on service architecture (SOA) can be well solved many of the problems. Different industry analysts or experts have different definitions and understandings for SOA. Gartner proposed SOA term and defined as follows: "Service-oriented architecture is a client / server software design method, which is applied by software services and software service users (also known as clients or service requesters). ". SOA is different from most of the general client / server models, which explicitly emphasizes loose coupling between software components, as well as their independent standard interface. The CBDI Forum defines "Service-oriented" (SO), focusing on service providing and management: "SO is the provision, use and lifecycle management of business and technical services, these business and technical services are self-description, loose coupling and It is achieved in a technical unique manner. "SOA describes a complete development model to help client applications are connected to the service. These modes customize a series of mechanisms for describing services, notifications, and discovery services, communicating with services. Unlike traditional application integration methods, all modes around the service are implemented in standard-based technologies. Most of the communication middleware systems such as RPC, CORBA, DCOM, EJB and RMI, are the same. However, their implementation is not perfect, there is always a problem in trade-off interactivity and standard customized acceptability. SOA tries to exclude these defects. Because almost all communication middleware systems have fixed processing modes, such as RPC functions, CORBA objects, and more. However, the service can be defined as a function, but also simultaneously defined an object, application, etc. This allows SOA to adapt to any existing system and make the system do not have to deliberately follow any special customization when integrating. SOA helps enterprise information systems to migrate to the "Leave-And-Layer" architecture, which means that the system can provide Web service interfaces outside the system without making modifications to existing enterprise systems, because they have been The application layer that provides a web service interface has been packaged, so SOA can quickly convert system and applications to services without modifying existing system architectures. SOA not only covers information from package applications, customized applications, and legacy systems, but also overrides features and data from IT architectures such as security, content management, search.
Soa-based applications can be easily added from these basic service architecture, so SOA-based applications can respond faster to market changes, in order to make new functional applications in enterprise business units. The main difference between the traditional enterprise application integrated architecture is that the system uses standard-based services and includes process / data services, arrangements, and combinations. Standard service is an integration point between applications. Services and combinations of services add the flexibility, reuse and integration of services. The following table emphasizes the difference between distributed component architecture and SOA: Table 1: Distributed service and service-oriented architecture comparison
