Shulou(Shulou.com)06/01 Report--

What this article shares with you is about how to understand micro-services. The editor thinks it is very practical, so I share it with you. I hope you can get something after reading this article.

Classify the types of services according to the business module. Each service can be deployed independently and isolated from each other. The service is invoked through a lightweight API. Services need to ensure good high availability.

How do you understand it? The following is my interpretation:

Split services by business, this is "vertical split"; at the technical level, "front and rear separation", belongs to "horizontal split"; horizontal and vertical cutting together, a single application is divided into small mesh applications, which is the embodiment of the "micro" idea in micro services.

Independent deployment and mutual isolation fully embodies the design concept of "I for all, everyone for me", which is the embodiment of the idea of "service" in micro-service.

With regard to lightweight API, microservices themselves recommend the use of lightweight communication protocols and simple data structures. In fact, http+json is usually used in the implementation process.

The advantage of this is that services no longer need to care about each other's model, but only through the pre-agreed interface for data flow. This is the embodiment of the idea of "decoupling" in micro-services.

The last point, which is more general, is something that must be considered in all kinds of designs nowadays. So I gave a definition of microservice, as shown in the following figure:

In order to do a good job of micro-service, it is necessary to do some preparatory work.

Talk about it from five specific aspects:

Business split, reflected in the design link: in the design, there should be sufficient judgment to reasonably plan the boundaries between services.

Service governance, the support of underlying technology: first of all, we should choose a distributed service infrastructure that suits our actual situation, and make corresponding technical preparations for service discovery, governance, circuit breaker and degradation.

Automatic testing must be automated. An obvious appearance of micro-services is that with the increase of services, if we continue to use the traditional testing model, we will encounter bottlenecks. In order to ensure efficient iteration, try to achieve more links to achieve automation.

Automatic operation and maintenance: after the micro-service is split, each service can be deployed independently, and in other words, it can be upgraded anytime, anywhere. Especially when the development of the Internet today, business to maintain an efficient response to market changes, automated operation and maintenance is an important link to improve the speed of delivery.

Monitoring: including hardware environment, service status, system health, interface calls, abnormal real-time alarm and early warning of potential problems, and so on. How important will monitoring be in the implementation of microservices? In a word: if you are not ready for monitoring, do not engage in microservices.

Finally, micro-service is not a silver bullet, there is no silver bullet in the software field, micro-service with its unique advantages to solve some problems, but also introduced other problems, the following points, we must think deeply and think twice.

The above is how to understand micro-services, the editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

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.