WebService advantages and disadvantages

Currently, SOA is the most popular topic in the IT field, while WebService is the most widely used technology in the SOA field, on the one hand, we are keen to use webserivce to solve the problem of Application Integration facing heterogeneous systems in enterprise applications. It was born as an integrated service and has become the first choice for Application Integration in heterogeneous systems ". On the other hand, good medicine is not a panacea. When we turn it down, we mistakenly think that to build SOA, we must use WebService to build services. after too many use of WebService, it is found that "taking too much medicine" may lead to "adverse reactions", causing serious performance bottlenecks for enterprise applications. What options should we make for its understanding and use?

SOA understanding

The essence of SOA architecture is not to say that packaging your applications or components into services is SOA, but to say that you need to be based on a framework, this allows your products to adapt to "business agility )". The important characteristics of SOA are loose coupling, reusable, visualization, and flexibility. Therefore, only after these steps can enterprise applications be truly placed in the SOA environment.

The SOA orientation is divided into two aspects: enterprise-oriented heterogeneous systems and enterprise-oriented internal business systems. The former is called inter-SOA, and the latter is called intra-SOA. In building SOA, enterprises should not only consider the upgrade and expansion of applications, but also the construction of new enterprise systems from the perspective of solving heterogeneous enterprise systems, using intra-SOA to adapt to rapid enterprise changes is not a long-term strategy, it can only be used as a last resort.

(Figure 1) Intra-SOA and inter-SOA Architecture

WebService values

WebService effectively solves the integration problem between application systems developed based on different platforms and languages, and becomes the most common and best technical means to solve inter-SOA. However, if the good medicine is useless, as long as we talk about SOA, we need to use WebService. Therefore, the "good medicine" takes too much medicine and is also poisoned. It is not a reasonable choice to encapsulate the business into a WebService to adapt to business changes when building an enterprise application or a new system.

A philosophy and value of Confucian culture is "the mean of the middle, too late ". We are facing the same attitude towards WebService.

Is there a technology that can adapt to both external environment changes and internal system changes? Therefore, intra-SOA and inter-SOA must be used internally and externally. The former solves business needs changes from the business perspective, the latter solves cross-system business and data integration at the system level. Intra-SOA and inter-SOA can be called a complete SOA solution by both internal and external repairs.

Tmaxsoft's SOA Approach

Currently, tmaxsoft provides a proframe Based on intra-SOA to build internal SOA for enterprises, at the same time, it also provides the inter-SOA-based ESB product Probus to solve the interface layer heterogeneous system EAI, workflow and multi-channel access functions, this provides a complete set of SOA enterprise-level solutions from the inside out.

Tmaxsoft divides the entire SOA framework into four layers: User Interface Layer (UI), interface layer (Interface), business layer (business), and data layer (data ), the interface layer provides inter-SOA-based solutions and intra-SOA-based solutions at the business layer.

(Figure 2) tmaxsoft enterprise-level complete SOA Solution

Proframe is the core solution that defines the business framework for generating and implementing SOA services. Proframe maximizes the flexibility, repeatability, and security required by SOA-based next-generation systems. Proframe's "Enterprise modulebus architecture" is a core tmaxsoft technology that uses Gartner's "microflows" concept to implement "intra-Soa. The ESB eliminates the dependency between systems and services and improves the reusability of services. Similarly, EMB eliminates the dependency between components or modules, thus improving the reusability of each module. A real service component is built by combining service interfaces, unit modules, and module processes built through ESB. EMB is not only reusable, but also visible to the Service's business logic. Therefore, users can participate in design and development without understanding programming. Among them, the core of proframe is EMB (Enterprise module Bus), which is different from the ESB (Enterprise Service Bus), but it is similar, it develops and defines the business logic of an enterprise on the proframe platform according to the business module and service module, and manages the service module in a unified manner through EMB, build an internal SOA environment by combining existing modules to generate various new services. These business modules and service modules can be reused and combined into new services to form a loosely coupled, reusable, and high-performance SOA environment within the enterprise.

(Figure 3) Enterprise module Bus Based on loosely coupled racks)

Services created with EMB are composed of loosely coupled modules, ensuring the independence of each module and the flexibility of the system structure. Loosely coupled components improve component reusability and maintainability.

Probus is an ESB solution in tmaxsoft's Inter-SOA. It connects or integrates services, applications, resources, and distributed service components to provide an ESB solution for reliable communication. It solves the problems of system interconnection, message transmission, conversion, routing, Web Service Support, and flow control. With a high-performance engine structure, Probus ensures stable services and can be connected with BPM and MCI. It flexibly supports multiple adapters and is an ESB solution that truly implements SOA 2.0.

We claim that we want to build an SOA, so the new system should follow a series of standards and support WebService. Many methods that can directly build a system using internal modules are very efficient. Now, for SOA, in order to support the calls of heterogeneous systems, it is the beginning of a nightmare to encapsulate it into a WebService. WebService communicates with each other based on the SOAP protocol. The data format transmitted by WebService is XML. XML format data must be transmitted and parsed each time WebService is called, these are the culprit of performance bottlenecks.

Summary

When we need to build a complex and efficient SOA environment, the performance problems caused by the communication methods and clumsy data exchange formats of WebService are doomed to make it a core position in the enterprise, tmaxsoft proframe provides an efficient SOA-based framework to build enterprise core applications based on proframe, while WebService is the preferred technology for inter-SOA in Enterprise SOA solutions.

Whether it is based on inter-SOA or intra-SOA, the purpose of implementing SOA is the same, that is, to achieve business-oriented, improve the flexibility of IT system expansion and reuse of IT assets, the service can be flexibly combined. WebService is the first choice in inter-SOA, rather than the Only Way to Solve SOA.