Three basic features of SOA

Three basic features of SOA

Independent functional entities
In a loose environment like the Internet, any access request may fail. Therefore, any structure that attempts to control over the Internet may face serious stability problems. SOA emphasizes the completely independent capabilities of functional entities that provide services in the architecture. Traditional component technologies, such. net remoting, EJB, COM, or CORBA all require a host (host or server) to store and manage these functional entities; when the running of these hosts ends, the service life of these components also ends. In this way, other application services running on the host will be affected when the host itself or other functions are faulty.

The SOA architecture emphasizes entity self-management and recovery capabilities. Common technologies used for self-recovery, such as transaction, message queue, redundant deployment, and cluster) it plays a vital role in SOA.

Low-frequency access to large data volumes
For. net remoting, EJB, or XML-RPC for these traditional distributed computing models, their service is provided through the function call method, to complete a function, you must call the function multiple times between the client and the server. In an Intranet environment, the impact of these calls on the system's response speed and stability is negligible, however, in the Internet environment, these factors are often a key factor that determines whether the entire system can work normally. Therefore, it is recommended that the SOA system exchange information with large data volumes at one time.

Text-based message transmission
The existence of a large number of heterogeneous systems in the Internet determines that SOA systems must adopt text-based instead of binary message transmission methods. In traditional component models such as COM and CORBA, a binary-encoded object is uploaded from the server to the client, and some functions are completed by calling the method of this object on the client; however, in the Internet environment, different languages and platforms have different definitions of data and even some basic data types, which makes it very difficult to transmit objects between different services. Because text-based messages do not contain any processing logic or data type, only text is transmitted between services, data processing relies on the acceptor to bypass the compatibility challenge.

In addition, for a service, the biggest difference between the Internet and LAN is that version management on the internet is extremely difficult, traditional software upgrades are almost impossible in this loose distributed environment. The text-based message transmission method is used. The data processing end can only process the part of the data that you understand and ignore other data to achieve ideal compatibility.