Differences between enterprise-level system architecture and tool-type Software Architecture

Today, my colleague asked me what is the use of web service in the system? What is the difference between it and the general direct writing on the client? What are the advantages?

It is really interesting to answer this question. Since I have asked this question, it means that there are some preconditions for not reaching an agreement. It is easy to explain the technology itself.

Therefore, we should first clarify the background of recommending the use of the SOA architecture, which is our internal informatization work. In this context, let's discuss whether SOA is good or not. Otherwise, SOA is not necessarily the best method.

Then we try to systematically analyze what is different from the general tool-type software architecture in the context of enterprise informatization.

First, the user groups are different. Tool software is often used by independent users. Enterprise-level systems often involve different positions and individuals. Most often, they involve jobs that require collaboration and managers who need approval. For example, a new project is only a new interface in a tool-type product. In an enterprise-level system, a manager often approves whether to allow new projects.

2. There are often multiple systems in the enterprise environment. There is a strong demand for integration between systems. Enterprise Users have high requirements on ease-of-use, but they are often unable to get down, often complaining and working. They also hope to improve, but they always don't know why the answer is no. Once they can be integrated, they can often solve many daily work complexity problems.

Third, data access concurrency requirements are different. Enterprise-level information systems usually require multiple users to operate data at the same time, and data can be shared by multiple users. Tool software is not like this. It is often accessed independently and can be protected independently.

Fourth, the deployment methods are different. The core of enterprise-level information systems is usually deployed on an independent server, and this server is required to provide services 24 hours a day. Tool software is often installed locally and can be turned on and off at any time.

Fifth, historical data requirements are different. Enterprise-level information systems often have high requirements on historical data and need to accumulate data at various times. In this way, data must be compatible when the system is upgraded. This is the migration. This is often not the case for tool software. Although many good software can be compatible with the old version of data, this is not mandatory.

In view of the differences above, we must consider these differences when conducting enterprise-level information system architecture. SOA is an architecture that meets these conditions. Based on the above differences, the technical points can have the following requirements:

1. integration between systems

2. After the system is deployed, try to reuse it.

Third, you need to consider concurrency Efficiency

4. Data Sharing

Next let's take a look at how SOA meets the above requirements.

Requirement	SOA	Similar Architecture Technology
Integration	Cross-Language Platform features	SOA, REST, DB
Reuse	Reusability	SOA, REST
Concurrency	Horizontal scalability	SOA
Share	Encapsulation	SOA, DB, REST
Security	Low Granularity	SOA, REST

Most of our capabilities are because the Web Service we use is based on xml technology and the architecture is directly obtained over the http protocol, such as compatibility and concurrency.

After talking about this circle, I also answered the first question. Isn't it? I recently want to share an enterprise-level information topic with you, so I think too much about it. Don't be surprised.