This article has been authorized by the author Zhang Liang netease cloud community.


Welcome to visit netease Cloud Community to learn more about Netease’s technical product operation experience.



If the journey of a project is like a journey into the unknown, the Cloud Native Application Architecture Practice is like a map of the obstacles that will be encountered along the way based on previous explorations, and how to overcome them.

Recently, I took advantage of the fragmented time to read through “Cloud Native Application Architecture Practice” written by my team.

As a solution architect, I feel that I have gained a lot, mainly from a systematic understanding of cloud native architecture, and understand the problems that a project may encounter in the whole process of growth from scratch, as well as the ideas, methods and tools to solve these problems.

This book begins with an introduction to the evolution of cloud native architectures and explains why enterprises should adopt native architectures. Then with the development of a business is usually path (i.e., from scratch, rapid growth to stable large applications), for example, about in each stage of the business objectives, enterprises in availability, scalability, maintainability, and safety requirements, combined with the actual business of netease experience, Suggestions are given, and explained the common techniques and tools.

If the journey of a project is like a journey into the unknown, this book is like a map of the obstacles you will encounter along the way and how to overcome them. And since the map has been walked by someone else, these problems are not imaginary, and the experience of solving them is the result of a lot of time, a lot of testing, and constant iteration and improvement. There were no fewer obstacles for those who got hold of the map, but there were fewer detours, and they arrived at their destination more calmly and confidently. That’s what I think is most valuable about this book.

These contents will enable us to have a more comprehensive understanding of the problems and solutions encountered in the development process of the project from small to large. When the project really encounters problems, we can have a good understanding of the key to the problem and the main solutions. We may not immediately use these knowledge, because the project at present may not have achieved so huge scale, but we can provide for the technical challenge ahead the necessary preparations, such as the project grows, and indeed, exposed to the problem described in the books, we don’t owe too much technical debt resulting in application or difficult to expand, Or it’s hard to co-develop, or it’s hard to maintain, or it’s so expensive to retrofit that it ends up hurting the business and paying a heavy price for not designing well in the first place.

The cloud, the microservices, the DevOps, these concepts have actually been around for a long time, especially the cloud, which has been a very hot topic in the last few years. People in the industry will feel that these concepts are already well known and nothing new. Because they use it every day, they practice it. But from many of my clients, that’s not the case. For example, some customers in traditional industries do not know what cloud computing is, and are not very clear about the benefits and risks that cloud services can bring. There are Web developers who don’t know about caching services like Redis. There are also a lot of developers who don’t know what a container is and what the benefits of using it are.

This is quite normal, because when these concepts were being heated up, most of the businesses of these customers did not have exponential user growth like those of Internet companies, with massive visits on Double 11, sudden traffic of seconds killing and buying, and peaks and troughs brought by drastic fluctuations of business. Thus there is no need for massive access to keep the service stable while keeping costs as low as possible. Because of their business have not encounter these problems, the elastic expansion, second class started, noise isolation, stateless services, service management, distributed applications, distributed transactions, and so on common technology in the large-scale Internet business, is a topic for their skills, or is optional, because the value is not high.

Now, however, they are starting to care. According to my observation, there are three main reasons for this:

  1. These customers see IT capabilities slowly becoming part of the core competencies of their companies, with some or all of their businesses relying on software to serve them or their customers.

  2. The client’s business has grown.

  3. The market is changing faster and faster, and customers need to adapt their business to the market as quickly as possible, so there is a need for rapid iteration of applications, easy collaborative development by multiple teams, as much automation as possible, less maintenance, and cost changes as the business evolves.

As a result, these customers are now facing the same problems as the big Internet businesses before them. In this case, the experience of solving these problems in this book can be of great help.

Of course, because the cloud native architecture involves a lot of technology, such as Web front end, load balancing, database, cache, CDN, monitoring, micro log collection, service and so on, each domain parsing can write more than one book, this book is not related to the principle of each technology, installation, configuration, use, maintenance and development, So we need to refer to other relevant materials for those.

In IT, technology is always evolving and new technologies are emerging. It is a safe bet that there will be technologies and products that solve problems better in the future. For now, this book is a cookbook worth reading for those looking for industry lessons and best practices in the cloud, microservices, and DevOps, so that we can apply those lessons to business development to solve our real problems and prepare for the adoption of more new technologies in the future.

Read more:

  • From DevOps to Cloud Native, all Cloud poses are unlocked

  • Second kill system design ideas based on cloud native

  • 360° Perspective: Evolution of cloud native architecture

  • Netease Cloud: 360° Perspective: Cloud native architecture and design principles


The basic cloud computing services of netease deeply integrate IaaS, PaaS and container technologies, provide elastic computing, DevOps tool chain and micro-service infrastructure services, help enterprises solve IT, architecture, operation and maintenance problems, and make enterprises more focused on business. As a new-generation cloud computing platform, you can click to try IT for free.


Understand the nature of DDoS protection: an intelligent system based on resource matching and rule filtering