Talking about SOA, Restful, Microservice, ServiceMesh, Serverless

Talking about SOA, Restful, Microservice, ServiceMesh, Serverless
SOA, Restful, Microservice, ServiceMesh, Serverless, these service models and design ideas reflect the continuous advancement of technology, and the ideas are not continuous advancement. From the original soa to serverless, the technology pioneers have been pursuing the flexibility of the system architecture. Sexual and intelligent.
The soa service-oriented architecture is a design specification, that is, company a wants to call the service of company b. At this time, a design specification is generated, which encapsulates the service of company a and communicates with the service of company b through an agreement. If company c has the same needs, then company a's services can be reused, soa is just a design specification, webservice's cxf, axis that implements this design specification.
RESTFUL is a design style and development method for web applications Based on HTTP, it can be defined in XML format or JSON format, which is a design specification. Each request uri is a kind of resource, and the operation of each resource corresponds to a different method. Get the resource, use get, modify the resource and use put, add post, delete and delete. According to the different methods, you can know the resource Operation method.
Microservice is a microservice architecture, which splits a complex single system into multiple web systems with a single business that can be deployed independently. Using this split can reduce the complexity of the system and increase the throughput of the system; The deployment is complex, distributed transaction processing is troublesome, and the management of microservices in different languages ​​is difficult.
Based on the difficulty of managing microservices in different languages, technology pioneers thought of a different language service that can be managed together. This architectural idea is servicemesh. Servicemesh is a service grid. Each service has a network agent. It only takes care of the business logic, and the communication is handed over to the network agent. The network control panel is used to manage multiple network agents. In this way, services implemented in different languages ​​can be managed. The technology pioneers feel that this is not enough, for development There are still many tasks for personnel, such as network agent management, service release and deployment, and testing. Developers do many things. Is there a way for developers to only focus on the writing of business logic code? Of course Yes, serverless is just such a framework. Developers only need to write business logic and leave other things to be done locally. This reduces the workload of developers and reduces communication time.
In short, the production of every technology has two sides. When we choose technology, only the technology that is suitable for the business is a good technology, and we cannot use it just because it is new.
Talking about SOA, Restful, Microservice, ServiceMesh, Serverless

Guess you like

Origin blog.51cto.com/xxdeelon/2536124