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

This article introduces the relevant knowledge of "what is the method of dividing micro services". In the operation of actual cases, many people will encounter such a dilemma. Next, let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Split pose 1. Posture one:

Hu Zhongxiang, a microservice expert on Sina Weibo, divides it from vertical and horizontal dimensions, simple and rude:

1.1 Longitudinal split

Split the business from the * dimension. The standard is determined according to the degree of relevance of the business, the closely related business is suitable to be split into a micro-service, while the relatively independent business is suitable for separate micro-service.

1.2 horizontal split

Split from the dimensions of public and independent functions. The standard is based on whether there is a common call by multiple other services, and the dependent resources are independently not coupled with other businesses.

Vertically based on the business, the relationship is ironclad together; the horizontal functions are independent together. I think if the split is so simple, you have the strength to dismantle it, dare you? So we continue to compare the remarks of other experts.

two。 Posture two:

Ali's friends from a comprehensive perspective, some of the dimensions will overlap with the above.

2.1 Service split to meet the needs of the business

Fully consider the independence and professionalism of the business, and avoid defining the service boundary by the team, thus the "bandits" grab the site and affect the trust of the team.

This dimension is similar to the above, but emphasizes the independence of business and team members, which is a good complement to the above.

2.2 the maintenance cost after the split is lower than that before the split

The maintenance cost here includes: manpower, material resources, time.

The cost here is an important link that must be considered for most small and medium-sized teams. If the input is not proportional to the income, or if it exceeds the leader's budget or market window, then advanced technology is a stumbling block. Do not be infatuated with technology. The so-called engineer thinking must not be.

2.3 splitting is not only the adjustment of the architecture, but also the adaptive optimization of the response in the organizational structure.

Ensure that the split service is maintained by a relatively independent team.

How do you understand this sentence? The traditional team division is divided horizontally according to the product department, front-end and back-end. after micro-service, the team may be the number of people who eat a pizza. The product, front-end and back-end are classified into services and the number of people is allocated with service as the center.

2.4 the most valuable result of splitting is to improve the scalability of the system.

Separate the services with different scalability requirements and deploy them respectively to reduce costs and improve efficiency. Such as full-text search services.

This is a bit similar to the above split by functional independence, which is actually extensible.

2.5 consider the frequency of software release

For example, 20% of the frequently changing parts are removed, and 80% of the parts that do not change frequently are deployed and managed separately. To put it bluntly, it is to be split according to the principle of 8Compact 2. The benefits of this split are obvious, which can minimize the sequelae of the release, such as user experience, service interference and so on.

But here is the question: what if 20% of the services belong to different business levels? So the split here should have a priority, and when splitting conflicts with each other, priority should be given to the one with a higher weight.

3. Posture 3:

The split given by Li Yunhua, a senior technical expert, in his architecture book:

3.1 based on business logic

The business in the system is identified according to the scope of responsibility, and those with the same responsibilities are divided into a separate service. This kind of business priority has appeared in the first two positions, which is the most basic and important division.

This is the end of the content of "what is the method of dividing microservices". Thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

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.