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

A brief Analysis of the Development Strategy of Micro-Services

Microservices have been very popular in recent years, so have you ever wondered what the motivation of microservices is? In fact, the most important motivation is that the business is changing too fast. Especially after the emergence of the mobile Internet, a variety of services: shared bike, Alipay, WeChat Pay and so on, the business is undergoing rapid changes and innovation, so the underlying application technology is required to support the rapid change of the business.

Let's take a look at the changes in the application architecture, which actually confirms the "fast" mentioned above from another point of view.

The first generation is a single architecture, of course, it has many problems, such as tight coupling, closed architecture and so on. The second generation is the SOA architecture, there may be many large enterprise applications, there are many kinds of support, in fact, when we see the SOA architecture, it already emphasizes loose coupling. So why did he emphasize this point? One of them is to be fast (not just for speed, of course). Up to now, the third-generation micro-service architecture has actually become more flexible. In the context of rapid business change, micro-service architecture is a very good solution, the core of micro-services-agility, flexibility, precision and flexibility. The greatest significance of the emergence of micro-service architecture is to continuously improve delivery efficiency and shorten the delivery cycle.

Martin Fowler, the most famous person of microservices, put forward the concept of microservices in 2015 (in fact, Netflix started to practice microservices in 2009, but there was no word microservices at that time). In 2015, Martin Fowler clearly put forward the concept of micro-service and defined it clearly, the most important of which is: small, independent, light and loose. That is to say, micro-services should be small, module boundaries should be clearer, and support independent deployment and independent evolution. Each micro-service should be able to deploy, evolve and upgrade independently. In addition, technology diversity is allowed, that is, in an overall application system composed of micro-services, each piece of business should be implemented with the technology that you are most suitable for, rather than uniformly using the same language. This is also a very important feature of micro-services.

Everything has two sides, that micro-service is not only good but not bad, it can also bring problems. In fact, it is obvious that, for example, from the point of view of operators, only one application is needed; after it is taken apart, multiple applications are needed, and the complexity and difficulty must be increased. From the developer's point of view, when writing a program, the calls between single applications and methods can solve a lot of business processing; after becoming distributed, it is necessary to make remote calls, not simple in-process calls. There will be some problems with calling it remotely, such as slower, less reliable than within the process, and so on. Then the developer has to deal with these problems and prepare for them. Another point that is also very important is the issue of data consistency. It turns out that in a single application, the database can be used to maintain the consistency of the data (or the transaction of the database to ensure the consistency of the data), but after the distributed system, it is suddenly found that this method is not working. Because data separation is advocated in the micro-service architecture, that is, each micro-service will have its own independent database. Martin Fowler also talked about allowing a variety of technologies, and at the data level, the most appropriate database technology should be used to build separate micro-services. It turns out that to ensure data consistency is a relational database, just use things directly. But when it comes to microservices, some microservices may use relational databases, but some microservices use non-relational databases. Therefore, under this premise, it is also a great challenge to ensure the data consistency of the whole system.

The above gives an overview of what the micro-service architecture is, what its characteristics are, and what its advantages and challenges are. Want to know more about microservices, Huawei Cloud College (https://edu.huaweicloud.com/)

A number of micro-service related courses have been online, from the introduction to basic knowledge, to the development of the first micro-service, to the launch and governance of micro-service, to take you to conquer micro-service in one stop, agile development of micro-service application, come and sign up for study.

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.