Ape Creation Call for Papers|[Cloud Native] Learning Cloud Native Experience Sharing

Blogger Nickname: Jumping Stairs Penguin
Blogger Home Page Link: Blogger Home Portal

Blogger's column page link: Column Portal -- Network Security Technology
Creation Original Intention: The original intention of this blog is to communicate with technical friends. Everyone's technology has shortcomings, and the same is true for bloggers. Ask for advice with an humility. Friends give guidance.
The blogger's motto: discover the light, follow the light, become the light, and emit the light;
the blogger's research direction: penetration testing, machine learning;
the blogger's message: Thank you for your support, your support is the driving force for me to move forward;

 

 1. Why is cloud native so popular?

1 Introduction:

Cloud native is a distributed cloud based on distributed deployment and unified operation and management, and a set of cloud technology product systems based on technologies such as containers, microservices, and DevOps.

The cloud is relative to the local. Traditional applications run on servers in the local computer room, while cloud applications run on the cloud (such as IAAS, PAAS, and SAAS). Native means native and home-grown, that is, the application is based on the cloud as soon as it is born, and can be run directly on the cloud platform or easily migrated to the cloud platform. We can define cloud native in this way: it is a new technology system and the future development direction of cloud computing.

For cloud native applications to run on cloud platforms, they must have the characteristics of the cloud, such as elastic scaling, distribution, rapid deployment, rapid iteration, high efficiency, and continuity. This is more than simply migrating applications originally on physical servers to virtual machines, not just infrastructure and operating platforms on the cloud, application architecture, application development methods, application deployment methods, and application maintenance methods must all be changed. Change.

2. Advantages

Quick launch, cloud development can be launched in the shortest time.

Focus on business logic

There is no need to pay attention to the front-end and back-end joint debugging and communication problems, and there is no need to consider the problems of operation and maintenance. Project complexity is greatly reduced.

Improve development efficiency

The cloud development model provides an API interface, through which data storage, file upload and other operations can be realized, which greatly improves the development efficiency. No need to learn a new language, just master javascript.

Elastic scaling

When performance requirements continue to increase, cloud development can elastically scale performance

3. Why the fire

Cloud native is completely popular. The reason for such popularity is that it makes full use of the elasticity, agility, resource pool and service-oriented features of cloud computing to change the design, development, deployment and operation mode of cloud applications. Provides great convenience. But at the same time, the development of cloud-native also brings security risks. This is cloud-native security. With strong technical research and development capabilities, cloud computing, big data, AI and other technologies are fully used to help enterprises solve cloud-native security problems.

2. Learning cloud native, what have bloggers experienced?

 

First of all, the cloud native thing, in which the docker container is based on the Linux operating system, and many people's programming is built under the windows window. If you are not familiar with Linux, the installation problems of some configurations under the cloud native are very big. A very torturous process. For me, I am more familiar with the Linux development system, and the relative development is also more convenient, which is also very helpful for cloud-native writing. However, it is still very complicated to build an environment, especially since most of us are used to the visual interface of windows, and there are still some places that cannot be bypassed for pure command execution.

Secondly, the concept of cloud native is relatively broad, docker containers, microservices, ks8, etc., where do we start? This is something that I was very troubled by when I first started learning, so the blogger looked for some videos on the mooc website and saw some course catalogues. This is also a quick way for us to enter cloud native learning and don’t know how to start, that is to find some books or The catalog of videos, it is very necessary to study according to the catalog, and it is also more effective for our study. The blogger also used this method to study here. After studying for two months, he found that this learning method is very efficient. Knowledge points can also be interspersed together, for the overall knowledge frame

In addition, in the cloud-native environment, a lot of content is actually very repetitive, and the repetition rate is very high on many blog platforms, so it is actually very troublesome for us to find suitable materials for us. It is very troublesome for each of us learners, and even once wanted to give up the idea of ​​learning. Here I want to tell you guys, persevere, and you can win until the end.

The way you applaud yourself is really handsome

Dear friends, persevering in learning is victory, learning this stuff, if you don't advance, you will retreat!

3. Study Suggestions

First of all, the blogger found a knowledge map for everyone here

 Most of the learning cloud native starts from Docker containerization. In fact, I personally think that it is not necessary to start learning from docker containers like everyone else, because there is a little trick to read more docker articles shared by others, in this article It is enough to learn how to build the basic framework and how to build a docker container. Later, you can start learning directly according to the microservices. When I was learning, I watched the MOOC video to learn, and basically I could find resources. The website of the . I need to think about which step is here. When I built a lighthouse asset management system based on docker a long time ago, I first came into contact with docker, and it took about 6-7 hours to complete the configuration. The problems that arise are as strange as they are.

Click the link on the right: Lighthouse Asset Management Construction under Docker Container

 Since I came into contact with this, it is very interesting to reproduce cloud native, and then I began to find various materials to learn, and finally I found that self-study by following the course catalog is the most effective method. So after a period of self-study, I posted my second cloud native.

 Click the link to learn

Docker+k8 microservice containerization combat

I wrote this article based on docker, service orchestration, CICD, microservice introduction, microservice peripheral, and microservice development. It is also a general framework for me to learn cloud native. I didn't expect the response to be very good when I wrote it. At that time, because the article was too long, it was divided into two parts to share.

1. Docker 2. Service Orchestration

1. Service dockerization 1.Kubernetes

2. Private warehouse management 2. Mesos

3. Service communication under Docker 3. Swarm

 

3. CICD 4. Introduction to Microservices

1. Gitlab triggers a build 1. Getting started with microservices

2. Jenkins pipeline 2. Advantages and disadvantages

3.Kubect operates k8s cluster 3.How to communicate

                                                                 4. How to discover, update and deploy

 

5. Peripherals of microservices 6. Development of microservices

1. SpringBoot 1. Service division

2.SpringCloud 2.rpc communication

3. Dubbo 3. Cross-language call

I still remember that when I wrote Gitlab to trigger the build, I installed both the Gitlab and Blue Ocean plugins. After researching for about a day, I checked a lot of information and did not solve the problem. In the end, I thought it might be a version problem. Immediately after switching the version Well, I often encounter this kind of problem, really, the inner roller coaster is really ups and downs.

The third part of the cloud native series was updated later

 Click the link on the right Docker+k8 microservice containerization combat (below)

 I didn’t expect this collection to be relatively high. Sometimes writing an article will always feel that no one reads it. It’s a very uncomfortable thing, but if you have a lot of collections, you will feel very gratified if you have a lot of people reading.

At that time, I remember that when I was writing about the Spring Boot microservices, my God, it was so difficult to reproduce, and I was completely dizzy. I couldn't understand how the core functions of Spring Boot should be implemented, which troubled me for a long time.

Although it seems that there are only two articles, the blogger has studied for about a month and a half before summarizing two articles.

I regret learning cloud native for a while, but I regret not learning cloud native for a lifetime

 The blogger is still mainly engaged in network security, and it is also because network security is exposed to cloud-native docker derivatives. So I spent about half a month searching for a lot of information to understand how cloud-native is used in the field of network security. Maybe it will be encountered in future work.

Learn the application of link cloud native in the field of network security

 In recent years , the concept of cloud security has gradually appeared in everyone's vision, so what is cloud security?

Baidu explained that "following cloud computing and cloud storage, cloud security has also emerged. Cloud security is a concept created by Chinese enterprises and is unique in the field of international cloud computing [1] . The " Cloud Security " plan is the information in the Internet age . The latest embodiment of security , it integrates emerging technologies and concepts such as parallel processing , grid computing , and judgment of unknown virus behavior . The information is sent to the server for automatic analysis and processing, and then the solutions of viruses and Trojans are distributed to each client. 

Personal understanding: It is to protect cloud projects and assets such as data, information, etc. The network security that we are familiar with is usually based on websites, systems, mobile devices, etc. In fact, in general, the protection of assets, the principle all pass

Subsequent cloud native articles have gradually begun to be refined. For example, the core technology of Kubernetes has recently been updated.

At present, two articles have been perfected, and there is another one that can be shared and played. Later, you can continue to refine the branches for sharing.

[Cloud Native] Kubernetes Core Technology (Part 1) Click to learn

[Cloud native] Kubernetes core technology (middle) Click to learn

 The process of bloggers learning cloud native is really tormenting, so I hope my article can provide some help for everyone's cloud native learning, thank you

Supongo que te gusta

Origin blog.csdn.net/weixin_50481708/article/details/126582531
Recomendado
Clasificación