[Entry series] relationship between soa and other technologies

SOA can be used together with many other technologies. However, component encapsulation and aggregation play an important role in it. As mentioned above, SOA can be a simple object, a complex object, a collection of objects, a process containing many objects, and a process containing other processes, it can even be the overall set of applications that output a single result. In addition to services, it can be considered a single entity, but in itself, it can have any level of complexity (if necessary ). For performance considerations, most SOA services do not fall to the granularity of a single object and are more suitable for large and medium-sized components.

Apart from XML and WSDL, SOA is not language-specific. You can use any programming language to implement services, as long as this programming language can generate services and can be used together with WSDL. Soap itself is not absolutely needed, but it is a general messaging system. Therefore, you can use almost any programming language and a platform that supports WSDL to implement Membership Services in SOA.

Applications Based on Common Object Broker Request Architecture (CORBA) have many components that must be connected to SOA. Although the Interface Description Language (IDL) in CORBA is similar to WSDL in concept, it is not strict. Therefore, you need to map it to WSDL first. In addition, more advanced SOA protocols (such as those used for process and policy management) are required, rather than similar concepts in CORBA. Remember that this is a situation where the CORBA Component (represented as a service) needs to interact with the SOA service; in the CORBA model, all the independent subsets can still work as before.

The model-driven architecture proposed by the Object Management Group and implemented in many IBM Rational products is highly correlated with the concept of SOA at a more abstract level. Based on this concept, any software process can be defined as a model or even a meta-model (that is, a model), and then these models and meta-models can be converted into actual components of the application. Therefore, MDA creates a model, which is first compiled into a software application, and then compiled into an executable program, so that it can run on the platform. MDA does not distinguish between services and objects. However, it does allow models to be composed of other subset models, similar to the process aggregation concept in SOA (a core component of SOA.

SOA and Web services are independent of programming languages, but Java is one of the main development languages. You can use well-defined Java interfaces and a variety of protocols for Java implementation to provide an advantage for developers who are building this model. Java is responsible for developing functions of each service, managing data objects, and interacting with other objects logically encapsulated in the service.

Another important relationship between SOA and web is the concept of autonomous computing and grid computing. The concept of autonomous computing is used to manage the scope of the distributed service architecture. Specifically, it helps maintain policies, service-level protocols, and the overall stability of the SOA system.

In addition, grid computing can be used with SOA systems at two levels. Grid is a form of distributed computing. It uses distributed features and interactions between services to provide computing support for SOA applications. In this case, the grid plays a role in the Framework, which implements some or all of the individual services. Therefore, SOA applications can be consumers of grid services.

On the other hand, the mesh itself can also be built on SOA. In this case, each operating system service is a member of the entire SOA application, and the SOA application is the grid itself. Therefore, individual grid components can communicate with each other using Web Services and interact with each other using SOA. In short, a grid system can be an SOA, or provide services to build an application-level SOA model on it.