Cloud Native, as we all know today, is essentially a set of best practices and methodologies for “using Cloud computing technology to reduce costs and increase benefits for users”.

Therefore, the term cloud native since its birth, to grow, and then to today’s great popularity, are in a continuous process of self-evolution and innovation.

Looking back, let’s take a broad look at the development history of cloud native. In the early days, due to the emergence of Docker, a large number of businesses began to be containerized and Docker-oriented. Containerization leads to the rapid growth of Devops through uniform deliverables and isolation; The emergence of Kubernetes makes resource scheduling decoupled from the underlying infrastructure, and the management and control of applications and resources began to come in handy. Container scheduling achieves resource scheduling and efficient scheduling. Subsequently, the service grid technology represented by LSTIO decouples service implementation and service governance capabilities.

Today, cloud native is almost “all-encompassing” everywhere, and more and more enterprises and industries begin to embrace cloud native.

As one of the practitioners of cloud native technology, Alibaba has long been one of the core technology strategies of Alibaba, which is derived from alibaba’s accumulation, precipitation and practice in the cloud native field over the past ten years.

Today, I would like to recommend a basic introduction to cloud native from Ali Cloud Habitat community, with a total of 14 chapters and 245 pages. Complete knowledge system, including first-line technical team cloud native technology best practices, with you to build your own cloud native skill tree.

[Full version here!!]

[Full version here!!]

directory

  • Chapter 1: What is Cloud Native?
  • Chapter 2: Basic container concepts
  • Chapter 3: Kubernetes core concepts
  • Chapter 4: Understanding Pod and container design patterns
  • Chapter 5: Application orchestration and management: core principles
  • Chapter 6: Application Choreography and management: Deployment
  • Chapter 7: Application orchestration and managing Job and DaemonSet
  • Chapter 8: Application configuration Management
  • Chapter 9: Applying storage and Persisting data volumes
  • Chapter 10: Snapshot storage and Topology scheduling
  • Chapter 11: Observability — Is your App Healthy
  • Chapter 12: Observability — Monitoring and logging
  • Chapter 13: Kubernetes network concept and strategic control
  • Chapter 14: Kubernetes Services

Kubernetes core concepts

Kubernetes has a business load check capability, which monitors the load on a business and allows it to perform a capacity expansion if the business itself is too CPU utilization or response time is too long.

Application Configuration Management

ConfigMap manages variable configuration information, such as the configuration files we apply, or its environment variables, or command-line parameters.

Its advantage is that it can decouple some of the mutable configurations from the container image, which also ensures the portability of the container. Take a look at the screenshot of the choreographer file on the right below.

Kubernetes network concept and policy control

In the narrow sense, runC container technology does not depend on any hardware. The execution basis of runC container technology is its kernel. The kernel representative of the process is task. A space isolation data structure (NSproxy-Namespace proxy) that does not require special Settings.

[Full version here!!]

Special statement: the material content comes from Ali cloud habitat community, copyright belongs to the original author, abuse deleted.