What changes micro-services bring to traditional architectures

As early as 1996, Gartner pioneered SOA (service-oriented architecture) concepts, and early SOA implementations were primarily webservice, built through contract publishing, contract description, and service implementation processes. Early SOA is mainly to solve the cross-development language and cross-platform interaction between software and software. In the traditional business, WebService is also considered as a top-up communication problem.

The proposed microservices (Microservice for SOA) are radically changing the original development architecture rather than complementing it. With the rapid development of mobile Internet, the speed of development and iteration is more and more fast. In particular, multiple terminals, the business of multiple platforms are growing rapidly. The traditional model development architecture of the monomer is obviously not and timely. The non-synchronization of multiple platform features is becoming more prominent. The coupling between business and interface is not completely solved, and there are more or less maintenance problems. The cost of the replacement interface and the migration platform has risen dramatically. Early people began to think there is no way to solve business logic and platform separation, they think of WebService and other RPC way, but the application process found that WebService private protocol is too heavy, on the mobile platform calls appear too time-consuming and laborious; So what about RPC? RPC standards are uneven, contrary to the Internet's open collaboration principle. Simply put: Traditional monolithic software does not really do a single development business, cross-device, cross-platform use. The code of the interface layer (P,VM,C layer in mv*) is constantly reconstructed, and the business coupling is not solved completely.

Micro-services spontaneously, through a simple HTTP protocol service, discard the previous stupid and heavy or incompatible service protocols. To better interact with the service, people recall Roy Thomas Fielding in his 2000-year-old proposed restful service architecture. Build a common service faster and better with a simple contract. Since then, the interoperability of the business has been well resolved, and companies are constantly experimenting with new architectures.

The business process is illustrated with a simple API document by exposing the calling interface of the business to granularity. Any consumer can use the business as quickly as possible. It does not have to be related to business details to quickly deploy the business to any consumer.

A result of microservices is that the server focuses on the Model layer, and the client focuses on the View layer and the Presenter or Controller or ViewModel layer, separating the focus and improving the efficiency of the development.

MicroServices can be deployed on any HTTP server as a traditional business without the need for special mechanisms, and can take advantage of the features of the HTTP protocol, as long as you can understand the basic characteristics of HTTP can be used quickly.

Traditional monolithic architecture (compact business logic, multi-technology mixed use)

MicroServices Architecture (Loose business logic, unified deployment or distributed deployment, one technology is all-encompassing)

What changes micro-services bring to traditional architectures