Shulou(Shulou.com)06/02 Report--

Original articles, welcome to reprint. Reprint please indicate: reproduced from IT Story Association, thank you!

Original link address: CICD of docker (final) (44)

From the beginning of writing advanced articles on September 11, 2018 to November 21 today, the harvest of advanced articles in a short period of 2 months is still full. Docker command is more and more familiar, jenkins is not mentioned in the intermediate text, this time also added the content of jenkins, in the intermediate text k8s, has been installing a lot of pits, so far you can successfully install k8s, and step by step installation to understand etc,apiserver,ControllerManager. But I still don't feel deep enough. I plan to continue k8s and practice next time. The emphasis is on practice and k8s.

Let's review together.

# the concept of microservices

Micro-services introduced from the evolution of software architecture, understand the concept of micro-services, know that the architecture of micro-services is not perfect, there are many advantages, independence (has its own independent stack), agility (fast iteration). The problem, the large number, the exponential increase, we have to consider how to communicate between them, and service scheduling is also what we need to consider.

Analysis of the problems brought by microservices, communication between services (one-to-one, one-to-many, synchronous and asynchronous), communication protocol dimension analysis of long-term protocols (restapi,rpc, message queuing), and comparative analysis of several rpc frameworks (thrift,dubbo,motan,grpc). Service choreography, first of all, uses a comparative way to show what traditional services and micro-services look like in service discovery, service update, service scaling, and understand why micro-services can not be supported like traditional services. Then the concept of service choreography is introduced.

The content of 3.springboot&springcloud, after all, they are all offline and closely related to micro-services, hesitation has a lot to do with micro-services, and beginners are easy to get confused, so that old guys have a key understanding of springboot and springcloud in their brains, what its mission is, its core content, and what role they play in micro-services.

Development of micro services

Analysis of the architecture of micro-services, but also developed a number of micro-services, in the development process, experienced springboot,springcloud,dubbo, cross-language RPC communication thift, and then this is just the beginning, in fact, it is all considered for service orchestration.

Prepare for service orchestration service dockerization of Docker composeDocker repository

Built a private warehouse, harbor.

When it's done, it just needs to be choreographed.

Learning itself is like learning Pang Tong. Learning one other is basically the same principle. It all starts from the beginning, to the architectural design, to the environment building, and finally to the deployment.

Mesos (MySes is not MeSes)

It started early and many big companies are still in use.

Docker Swarm

It's already in the docker installation. Official authentic.

Kubernetes

The threshold of hesitation kubernetes is relatively high, we spent several times of the previous framework to study it, but to be honest, it is not fully understood, in order to make you better understand. Two deployments, one non-authentication authorization and one authentication required. In fact, authentication is ssl. Haha. The k8s cluster is built by hand in one module. Then an official example is demonstrated on the cluster.

CICD&Devops

Finally, I experienced CICD and Devops, and the relationship between them is still very close. Service choreography provides the soil for Devops landing. Service choreography is actually created for CICD and Devops. Set up the deployment of gitlab and jenkins.

The pipline pipeline script and the shell script written in the pipeline are written under jenkins. Experienced CICD, from the submission of the code to complete packaging, image, push push. Finally, complete the update of the service. Finally, never use jenkins containers. This thing is not suitable for containers.

PS: from what I see here are basically true love buddies, thank you from the bottom of my heart. From docker beginner, intermediate to advanced. It has been more than 7 months since I learned about docker in April, and the persistent study of docker has been going on, and some old friends have pointed out the problems in the article. Thank you for having you all the way! I sincerely hope that the article I wrote will be helpful to all of you. There is a picture of beach footprints in front of the article. I hope that when we learn docker together, you and I will let more people go together. Thank you for being willing to share my article with me in the process, so that more people will be on the road of docker. We've been on our way. Work together! Are you tired? just be tired, because at least it proves that you are still alive! The next step is to learn docker will not stop. Continue to open our practice articles through online open source projects to complete the deployment and operation and maintenance under the docker environment.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.