Container concept and cloud native

Container related

Summary of development history

1979 year ,Unix v7 System support chroot, Build a separate virtual file system view for your application .
1999 year ,FreeBSD 4.0 Support jail, The first commercial OS Virtualization technology .
2004 year ,Solaris 10 Support Solaris Zone, The second commercial one OS Virtualization technology .
2005 year ,OpenVZ Release , Very important Linux OS Virtualization technology pioneers .
2006 year ,Google Open source internal use process container, It was later renamed cgroup.
2004 year  ~ 2007 year ,Google  Internal mass use  Cgroups  Waiting OS Virtualization technology .
2008 year ,Cgroups  Into the  Linux  Kernel mainline .
2008 year ,LXC（Linux Container） The project has Linux The prototype of the container .
2011 year ,CloudFoundry Development Warden System , A complete container management system prototype .
2013 year ,Google adopt Let Me Contain That For You (LMCTFY)  Open source internal container system .
2013 year ,Docker Project officially released , Give Way Linux Container technology is gradually gaining popularity in the world .
2014 year ,Kubernetes Project officially released , Container technology begins with choreography .
2015 year , from Google,Redhat、Microsoft And a number of large cloud vendors co founded CNCF, The original wave of cloud starts .
2016 year -2017 year , The container ecology began to modularize 、 Normalization .CNCF Accept Containerd、rkt project ,OCI Release 1.0,CRI/CNI There is broad support .
2017 year -2018 year , Commercialization of Container Services .AWS ECS,Google EKS,Alibaba ACK/ASK/ECI, Huawei CCI,Oracle Container Engine for Kubernetes;VMware,Redhat and Rancher Start offering based on Kubernetes Business service products of .
2017 year -2019 year , Container engine technology is developing rapidly , New technologies are emerging .2017 end of the year Kata Containers Community establishment ,2018 year 5 month Google Open source gVisor Code ,2018 year 11 month AWS Open source firecracker, Alibaba cloud releases security sandbox 1.0.
2020 year -202x year , Container engine technology upgrade ,Kata Containers Start 2.0 framework , Alibaba cloud releases sandbox containers 2.0…

Isolation idea

Derived vessel specification

OCI Runtime Spec： Container runtime specification , To specify the configuration of the container 、 Execution environment and life cycle . The configuration file of the container is named  config.json, It also contains a series of configuration information of the container . The execution environment is defined to ensure that the application running in the container has a consistent environment with the runtime , And define standard common operations for container lifecycle management . 
OCI Image Spec： Image format specification , from  4  Block content consists of ： detailed list （manifest）、 Mirror index （image index）、 To configure （configuration） And file system layer （filesystem layers）. Listing describes the metadata of the image . The mirror index is optional , Pointing to different platforms  manifest  file , It is equivalent to the entry of the entire image , From this file, you can get all the file information that the entire image depends on . The configuration saves the hierarchical information of the file system , And some information the container needs to run . The file system layer describes how to  layer  Stack into a complete file system , And how to use  layer  To indicate changes to the document . 
OCI Distribution Spec： Mirror distribution specification , Defined a set  API  Protocols are used to facilitate and standardize the distribution of content .
CRI：Container Runtime Interface, Container runtime interface , It is the interface between the container choreography system and the container engine . 
CNI：Container Network Interface, Container network interface , There is a set of tools used to configure  Linux  Container network interface specification and library composition , It also includes some plug-ins . Only care about the network assignment when the container is created , And releasing network resources when the container is deleted . The interface has only four methods ： Add network 、 Delete network 、 Add network list 、 Delete network list . 
CSI：Container Storage Interface, Container storage interface , It is the interface between container orchestration system and container storage system . Shimv2： This is used to dock virtual machine based containers （ Such as  Kata） Interface specification .
 After these specifications are established , Concrete implementations based on these standards and specifications are emerging , A hundred flowers are in full bloom .Docker  In order to adapt  OCI  The standard specification separates two standardized components , One is called  runc, One is called  containerd. Let's take a look at these two components .

Container operation process

1. Download mirroring

2. Unzip the image into the file system package

3. Run the container from the extracted file system package

Old version delivery and container delivery

Service related

Iaas pass saas

 What's the difference between them ？
IBM  The software architect of  Albert Barron  I used pizza as a metaphor , Explain the problem .David Ng  Further extension , Make it more accurate and understandable .
 Imagine that you are a catering business , Going into pizza business .
 You can go from beginning to end , Make your own pizza , But it's more troublesome , There are many things to prepare , So you decided to outsource part of the work , Use other people's services . You have three plans .
（1） Scheme 1 ：IaaS
 Others provide kitchens 、 stove 、 Gas , You use the infrastructure , Come and bake your pizza .
（2） Option two ：PaaS
 Besides infrastructure , They also provide pizza crust .
 You just sprinkle your own ingredients on the crust , Let him bake it for you . in other words , All you have to do is design the taste of pizza （ Seafood pizza or chicken pizza ）, Others provide platform services , Let you realize your design .
（3） Option three ：SaaS
 They made pizza directly , You don't have to step in , What you get is a finished product . All you have to do is sell it , At most, pack it again , Print your own  Logo.

Iaas->pass->saas

Ipaas apaas

iPaaS Tend to IaaS and PaaS Between

Ø Due to the variety of enterprise stacks SaaS Software , Using different hosts and databases , How to integrate these software ？ This requires a technology , That is to say iPaaS.

Ø Solve the barrier problem caused by various software in the enterprise , reduce IT The amount of work ——ipaas

Ø Focus on getting through , Integrate and manage existing platforms .

aPaaS Tend to PaaS and SaaS Between

Ø How to provide a framework , So that business people can design a management software without learning code ？ This pattern is apaas, Start from the application and data level , Design and build tools and logic , Realize zero code development .

Ø Meet the flexible but cost-effective software development pursued by enterprises , Lower the development threshold ——apaas

Serverless（BaaS、FaaS）

What is? Serverless Architecture? ？

according to CNCF Yes Serverless Definition of calculation ,Serverless Architecture should adopt FaaS（ Functions are services ） and BaaS（ The back-end service ） Services to solve problems , Is an inclusive but not limited relationship .

BaaS（Backend as a Service, Back end as a service ） It means that we no longer write and / Or manage all server components   for example ： Face recognition , Message sending, etc .

FaaS（Function as Service, That is, function as service ） for example ：aws Lambda（serverless framework ） 

Cloud primordial acquaintance

Definition

elements

Microservices ： The benefit of the microservice architecture is to function After cutting , Service decoupling , Better cohesion , Change is easier ; Another technique for dividing services is said to be based on DDD Come on .

Containerization ： Containerization provides implementation guarantee for microservices , Play the role of application isolation .

DevOps： Development and operation and maintenance integration , actually DevOps Testing should also be included ,DevOps Is an agile mind , It's a culture of communication , It's also the form of organization , Provide continuous delivery capabilities for cloud natives .

Service Grid ： Service grid is an infrastructure layer , Used to handle inter service communication . Cloud native applications have complex service topologies , The service grid ensures that requests travel reliably through these topologies . In practical application , Service grid is usually composed of a series of lightweight network agents , They are deployed with Applications , But transparent to applications .Service Mesh Components .

Summary of the development stage of Yunyuan

CNCF Panorama

CNCF, Full name Cloud Native Computing Foundation（ Cloud native Computing Foundation ）, The slogan is   Adhere to and integrate open source technologies to choreograph containers as part of the microservice Architecture  , As an important force committed to the promotion and popularization of cloud native applications , Whether you're a cloud native app developer 、 Both managers and researchers need to understand .

CNCF As a firm neutral Foundation , betake Github The promotion of fast growing open source technology on the Internet , Such as Kubernetes、Prometheus、Envoy etc. , Help developers build excellent products faster and better .

Alibaba cloud native panorama