Shulou(Shulou.com)05/31 Report--

Today I will show you the difference between microservices and SOA. The content of the article is good. Now I would like to share it with you. Friends who feel in need can understand it. I hope it will be helpful to you. Let's read it along with the editor's ideas.

MSA vs SOA

1.ESB (enterprise service bus)

From the name, we can know that its concept draws lessons from the communication model in the computer composition principle-bus. All the systems that need to communicate with external systems are connected to ESB, which is perfectly compatible with the existing heterogeneous systems that are isolated from each other. We can use the existing systems to build a new loosely coupled heterogeneous distributed system.

However, in practical use, it still has many shortcomings. First of all, the ESB itself is very complex, which greatly increases the complexity and maintainability of the system. The second is because ESB wants to make all services communicate through one channel, which directly reduces the communication speed.

In modern micro-services, using lightweight communication mechanism, each service has its own processing logic. It knows where the service it is looking for and what it does not need to do on the communication link.

two。 The concept of service and the size of service

In fact, the emergence of SOA is to solve the historical problem: there will be a variety of isolated systems in the process of informatization, and there needs to be a mechanism to integrate them, so there will be the emergence of ESB mentioned above. Similarly, the initial service of SOA is a big concept, usually specifying a system that can operate independently (in this way, it seems that there is a natural loose coupling between services). This is equivalent to "serving the subsystem".

On the other hand, the micro-service has no historical burden and is light, and the size of the service is usually not too large. In practice, it is often that a service should be able to represent "an indivisible or inseparable business entity in the actual business scenario". Controlling the size of the service to a smaller volume can bring a lot of benefits.

3. Communication protocol

Nowadays, more and more projects begin to use RESTful as the basis of API design, but only a few years ago, a large number of API used Web Service of XML-based heavyweight protocols such as SOAP, WSDL and so on. This is more or less the same as the two points mentioned above. If you think about it, they are all caused by historical reasons. Similarly, after years of development, there are basically two mainstream communication protocols:

The RESTful specification based on HTTP is the most widely used text protocol.

Lightweight binary protocol Thrift, Protobuf, or any custom lightweight protocol

Advantages of MSA

1. The service granularity is small, the implementation is simple, and it is easier to achieve low coupling and high cohesion.

two。 Distributed deployment, maintainable independently

3. When there is a lot of pressure on a service, you can add instances to achieve horizontal scaling.

4. It is easier to focus on the actual business scenario

The above is the whole content of what is the difference between micro-services and SOA, and more content related to the difference between micro-services and SOA can search the previous articles or browse the following articles to learn ha! I believe the editor will add more knowledge to you. I hope you can support it!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.