Are microservices necessary for php?

Technical circles often generate new buzzwords, and it is easy to be misled. The most frightening thing is that some technical teams just follow the buzzword or move closer without understanding it, as if they are afraid that if they do it themselves Technology and buzzword are not related or the same, they are very low. I feel that this phenomenon is too common in the technical circle, and some people are not happy about it. I will write an article to express my views.

When it comes to the buzzword of microservices, I must admit that until now I have not understood the difference between it and servitization. I can’t even figure out what Taobao did in 2008. Is the SOA system formed after the service-oriented transformation done in 2016 the same as the current buzzword? In various articles, microservices are simply promoted as the savior of some scenes in the technology world, which directly misleads a lot of people. Students must develop a microservice system when they come up. (Recommended learning: PHP video tutorial)

But I don’t know how many students have thought carefully about whether it is necessary or not. Is using microservices a help or a problem for business development? In the Internet-type business that rapidly iterates, the iteration efficiency of the business is the core issue.

Based on my own understanding, my view on servitization has always been that if you can avoid entering this pit, it is best not to enter. The complexity of a single application is far greater than that of a distribution composed of N applications. The traditional system is much simpler and faster. Once you enter the distributed pit, you have to make a relatively large investment in technology.

For some small and medium-sized companies, I think it is completely unnecessary. Jeff Dean of Google once shared his views on Google’s service-oriented approach:

Let Google has the ability for thousands of people to collaborate on development in parallel. Before seeing this point of view, I always felt that servitization focused on solving the problem of horizontal scalability, followed by the problem of parallel collaboration.

But now I basically agree that the focus of service-oriented is to enable a company to have the ability of parallel collaborative development of more than a hundred people. I think that with dozens of R&D students, parallel collaborative development will not be a big problem. , the investment in parallel collaboration at this time will be much smaller than the investment after entering servitization.

So when some friends asked me whether the company should change to service-oriented, I always asked two questions:

How many people are there in the company’s R&D team now?

What is the current horizontal scaling bottleneck?

If servitization is not the core bottleneck in these two issues, or it can be solved with only a small cost of people or machines, I would strongly recommend not to do servitization, so please accept the microservices Students who are tempted by buzzword, please think carefully before adopting such a structure. The strategy should be to try not to use it to deduce the costs and problems that will arise. If the costs and problems are not that big, don’t use.

Unless it is absolutely necessary, please make arrangements in terms of organization and team personnel to truly implement service-oriented services, and do not let this eventually become an obstacle to business development.

The above is the detailed content of Are microservices necessary for php?. For more information, please follow other related articles on the PHP Chinese website!