foreword
What exactly is cloud native? Cloud native is a very hot word. I have read a lot of information about cloud native, but many friends still don’t quite understand what so-called cloud native is. This article will tell you how the author understands cloud native.
cloud native
Many children are particularly interested in cloud native, but they have heard this word a lot, and they still don't know much about what cloud native is. Baidu Encyclopedia can find the entry of cloud native as follows:
Cloud native is a technical system based on cloud technology, distributed deployment, and a set of systems based on container, microservice, DevOps and other technologies.
Cloud native = cloud + native
Having said that, there may still be a large number of friends who are still at a loss and don't know why. It’s okay, don’t go to Care too much; I’ve seen a lot of online materials explaining cloud native, and I’m just as confused as everyone else; as far as my personal best experience after the understanding process is concerned; my understanding as follows:
Cloud native is translated from "Cloud Native"; and it is translated quite well.
Cloud native is composed of two words; that's right, cloud native = cloud + native; the former means that the technical system of this technology is represented by the cloud, which can be simply understood as the cloud native technology is manifested in the cloud, and applications are deployed In the cloud; native (Native) means that the means of implementation is inherently with the characteristics of cloud services, without additional features, which may be difficult to understand.
But comparing springcloud may be easier to understand; SpringCloud also provides cloud service system support, but when we use springboot to develop our microservice components, we need to use a lot of code or injection mechanism to make our microservice components support certain Aspect cloud characteristics; Although this method also achieves the purpose of cloud services, the functions of these cloud characteristics are supported in components. If we want to optimize cloud characteristics, our microservice components must inevitably be modified; Native advantages It was immediately reflected that since the cloud-native system already supports it, the microservices we develop do not need to consider these cloud features, as long as they are developed and deployed in the cloud-native system, they will be supported; Put it back to the original place; this way it may be easier to understand the word native. Serverless and service mesh also have similar considerations. Native (native) allows our applications to take into account the cloud environment from the beginning of the design, designed for the cloud natively, running in the best posture on the cloud, and making full use of the flexibility and distributed advantages of the cloud platform.
The four elements of cloud native
Containers, microservices, DevOps, and CI/CD are actually the four elements of the cloud-native basic system. Personally, I think it can only be said that they are the four technical directions used in the implementation method of the cloud-native system at the current stage; it does not mean that cloud-native is These 4, but refer to, at the current stage, cloud native is realized through these 4 systems. Of course, such a fresh and powerful technical system is the development direction of cloud computing in the future.
Serverless
Serverless refers to the concept of building and running applications that do not require server management. That is to say, developers do not need to pay attention to the underlying infrastructure, but only need to pay attention to the business of the application, and the service can be automatically expanded.
Service Mesh
Service Mesh business logic is decoupled from non-business logic, achieving the great goal of only focusing on business logic in development. It expresses the same meaning as Serverless above; but the dimensions are different; Serverless emphasizes the dimension of the cloud-native basic layer; Service Mesh refers to the cloud-native application layer; it decouples the features that have nothing to do with business logic in the application layer ( Such as service discovery, routing, load balancing, current limiting and degradation, etc.); put it in a separate Proxy (such as K8s Side car), and only focus on business logic as application development;
conclusion
This article mainly introduces the author's personal understanding of the very popular technical term "cloud native"; and boldly talks about his personal outlook on cloud native technology; cloud native technology is undeniable; it is on the road of technological development, and it will be necessary A period of technical history; of course, it is also the current direction of cloud services and the visible development of cloud computing in the future. I hope that friends who are interested in and concerned about cloud native will discuss cloud native topics together; everyone is welcome to leave a message, write down your views, impressions and technical points you want to know, and we will explore cloud native technology together.
Thank you for your continued attention.