Docker+kubernetes (k8s) micro-service container Practice

Source: Internet
Author: User
Tags k8s


The 1th chapter first Knowledge Micro Service
Micro-service, we start from the traditional single structure, to see what kind of environment and needs to step into the micro-service, and then specifically to understand what is the micro-service, so that the concept of micro-services have a deep understanding. Then we draw together a micro-service architecture diagram, and then from the architecture to analyze the advantages and disadvantages of the micro-service architecture. ...
1-1 MicroServices-Guided Learning
1-2 evolution of the software architecture
1-3 What is Micro Service
1-4 drawing a micro-service architecture diagram
1-5 advantages and disadvantages of micro-service architecture

2nd the problem and solution analysis of micro-service
Learn by comparing traditional services with microservices, and if you encounter any problems with microservices architectures, there are solutions to these problems in the industry. We then inserted a section of Springboot and Springcloud, the main purpose of which is to make it clear how they relate to microservices, the relationship with Docker, and the relationship with service orchestration. ...
2-1 Micro-Service architecture issues
2-2 how to communicate in micro-service rooms
2-3 service discovery, deployment updates, and capacity expansion
2-4 Springboot&springcloud (Upper)
2-5 Springboot&springcloud (Lower)

3rd. Micro-Service development
Let's start by assuming a business scenario, analyzing the division of microservices, what each microservices does, how they are dependent, and how they communicate. Then starting from 0, one line does not fall in the development of a complete service. Service development process We will use Springboot, use to Dubbo, use to thrift, use the API Gateway Zuul. ...
3-1 Micro-service Business Analysis
3-2 THIRFT Installation and verification
3-3 Python Development Information Service
3-4 Developing User Services (top)
3-5 Developing User Services (next)
3-6 Development User Edgeservice_a
3-7 Development User Edgeservice_b
3-8 Development User Edgeservice_c
3-9 Development User Edgeservice_d
3-10 Dubbo Introductory Drills (UP)
3-11 Dubbo Introductory Drills (bottom)
3-12 Development Course Services
3-13 Development Course Edgeservice
3-14 Apigatewayzuul

Chapter 4th Prelude to service arrangement
To prepare for the service orchestration, first we docker all microservices and then use the native Docker-compose to run them in the container and ensure that they can communicate with each other in the container as well. Finally we set up a private warehouse to store our mirrors, using the industry's mainstream-harbor. ...
4-1 service Docker (top)
4-2 Service Docker (next)
Service communication under 4-3 Docker (UP)
Service communication under 4-4 Docker (bottom)
4-5 mirrored warehouses
4-6 three big platforms set sail

5th Chapter Service Orchestration-mesos
We go from concept to architecture design to scheduling strategy to understand Mesos, and then draw the Mesos cluster architecture diagram We want to build, then refer to the schema diagram we set up the entire cluster environment, finally adjust our microservices, deploy them in the Mesos cluster.
5-1 Learn Mesos
5-2 Draw the Mesos cluster architecture diagram
5-3 Cluster Environment Construction _a
5-4 Cluster Environment Construction _b
5-5 Cluster Environment Construction _c
5-6 Adjusting the micro-service adaptation Mesos
5-7 Micro-Service Deployment _a
5-8 Micro-Service Deployment _b
5-9 Micro-Service Deployment _c

6th Chapter Service Orchestration-dockerswarm
The process of learning is similar to Mesos, which is to start with the concept, understand the architecture design of swarm, understand its service discovery, service orchestration, and then build swarm cluster environment, then adjust our microservices to adapt to swarm, and finally deploy them in the swarm cluster.
6-1 Learn Swarm
6-2 cluster environment Construction (top)
6-3 Cluster Environment Construction (next)
6-4 adjusting microservices and service configuration
6-5 Micro-Service deployment

7th Chapter Service Orchestration-kubernetes
The whole idea of kubernetes learning is also from concept to cluster building and finally to micro-service deployment. But because of its leadership in the field of service orchestration and its high threshold. We peel it into three parts, the core part, the KUBE-PROXY&KUBE-DNS, the authentication authorization. Gradually through the gradual infiltration of the way, not only to make it easier for everyone to get started, but also to have a deeper understanding of it. ...
7-1 Learn kubernetes (UP)
7-2 Learn Kubernetes (next)
7-3 Prelude to environmental construction
7-4 Pre-readiness environment
7-5 base cluster Deployment (top)
7-6 base cluster deployment (bottom)
7-7 Small trial Sledgehammer
7-8 Kube-proxy and Kube-dns
7-9 Understanding Authentication, Authorization
7-10 adding authentication authorizations to the cluster (top)
7-11 adding authentication authorizations to the cluster (bottom)
7-12 try again Sledgehammer
7-13 Deploying our micro-services

8th Chapter CICD and DevOps
Start with a practical perspective on why you should have CICD and DevOps, and then essentially understand the concepts of CICD and DevOps. Then we analyze what the CICD process is like. Finally, we build a gitlab,jenkins environment, combined with mirrored warehouses and kubernetes clusters, to construct a fully automated process from code submission to service updates. ...
8-1 Understanding Cicd and DevOps
8-2 Preparing Gitlab and Jenkins
8-3 Cicd Practice (UP)
8-4 Cicd Practice (bottom)

The 9th chapter of the course summary
A summary of what has been learned in the previous section.
9-1-Course Summary

: Baidu Network Disk download

Docker+kubernetes (k8s) micro-service container Practice

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.