On July 19, 2018, my first book, Spring Cloud Microservices – Full Stack Technology and Case Study, was sold. This is a memorable day, but also to their usual study assessment.

In recent years, it is micro service fire, I also count hug hug thigh, as a technical person, must always keep the heart of learning, is the so-called move when the move.

Micro service is so popular, is no doubt to solve our actual work encountered a lot of pain points. For example, there are many duplicate codes, bloated projects, and long startup time.

Today I will talk about my understanding of microservices and my attitude towards technology.

Microservices architecture is an architectural concept that you can build with Spring Cloud or Dubbo, regardless of language or framework.

My idea of microservices is to split and simplify. Just like the development of a company, at the beginning, several people formed a studio, one person as three people, everything to do. Then it grew to 50 people, divided into several divisions, each with its own focus. When it gets bigger, there will be many groups within a department. We can think of each group as a service, they focus on a certain piece of work, there will be cooperation between the groups. All of the little pieces add up to this company.

The same is true of the architecture. At the beginning of a project, all the functions are added to it, and the code quantity is large and the functions are complex. If something goes wrong, the whole system will be affected. I am not an expert, what I said is not necessarily right, you just understand it.

Micro services is not as mysterious as you think, big companies can do it, small companies can do it. Whether you can successfully implement microservices depends on your technology leaders and your own attitude towards technology.

In fact, I am an open person, not always confined to some old technologies, but like and willing to try to use new technical frameworks in my work.

A good framework will come in handy and improve development efficiency. The most important thing is to keep up with the trend. Technology changes so fast that as a developer, you have to keep learning to stay relevant.

Recently I read an article called why many big companies are still using old technology? This is a problem at the corporate level, where the cost of refactoring is too high. There is also the argument that any technology architecture that is out of business is rogue, which it is, the right thing to do at the right time.

I don’t think there is anything wrong with what is said above. Your leader is under pressure from the company and will not say that it is necessary to spend a lot of money on reconstruction in order to use some new technologies.

However, from the perspective of the average developer, if you keep using old technology, you will find yourself lagging behind when you change jobs. Of course, you can also work hard and learn by yourself, the interviewer will say that you don’t have practical experience. It’s not that I want to learn, it’s the reality.

I still encourage you to try new technology bravely, difficulties are not terrible, terrible is that you do not have the opportunity to solve the difficulties, only continue to step on the pit, in order to achieve excellent you.

Small and medium-sized teams play micro services, not too many lofty functions, enough to support the development of business on the line. For example, if your product does not have much traffic, to be honest, there is no difference between limiting traffic and limiting unlimited traffic. Why waste so much time on limiting traffic? It is better to spend time on improving the function of the product.

Of course, it is not to say that flow limiting is not important. In case of emergencies, in case of rapid business development, rapid increase of requests, and frequent system flushing, flow limiting is very important at this time. What I want to express is that we should do the right thing at the right time, and we must take precautions when conditions permit.

In the process of implementation, we can learn from the successful cases of some excellent companies, design the architecture that meets the business development based on the company’s own business, and select the appropriate framework to build microservices based on the company’s technology stack.

Is the so-called “army and horses did not move, grain first” **, the company did not move, self first. Geek Time recently launched the column “Learn Micro Service from 0”, in which Mr. Hu Zhongxiang, the architect of Sina Weibo, shares his experience and perception in the process of micro service architecture.

I read the syllabus carefully. It’s very comprehensive. It is divided into four modules, each of which has a lot of content and a wide range of knowledge.

  • Module 1 mainly explains the basic principles of micro-service, in-depth analysis of micro-service, let you know what is micro-service, how to do monitoring, tracking and other knowledge points. Dubbo will be taken as an example to analyze the concrete implementation of microservices architecture.

  • Module 2 is all about actual practice, which can be called ‘microservices best Practices’. This includes recommendations for selecting the registry and RPC framework. The server is faulty or the client fails to be invoked.

  • Module 3 is about how microservices do Docker containerization and DevOps. Simplify the publishing process through containerization and DevOps, and build resilient scaling architectures.

  • Module 4 Outlook on microservices, what will the future of microservices look like? What a surprise it will bring us. As the next generation micro-service architecture, Service Mesh is definitely in place. I am also looking forward to what Service Mesh looks like in Mr. Hu’s eyes.

I bought it myself to learn from the excellent experience of my predecessors. Readers friends if interested, welcome to long press the two-dimensional code to identify the poster to buy, the price is more appropriate. It seems that I will get the cash back amount if you buy it. If you have bought it, please tell me. After the cash back is given to me, I will return it to you to reduce your learning cost.

A personal introduction of Mr. Hu

Hu Zhongxiang is the architect and technical director of Weibo servitization project. Since joining Weibo in 2012, he has been responsible for the upgrade of weibo counter architecture, the service guarantee of Spring Festival Gala and Olympic Games, and the upgrade of Weibo Feed business architecture. At present, I mainly focus on the direction of service, including: micro-service governance, flexible scheduling and automatic monitoring.