The goals and future of multi-cloud and cloud native computing
- processing the packaging, deployment, and execution of the application ‘on its own’ on the cloud
- Scale-up/down can increase the deployment size when the application demand increases and withdraws the deployment when the application demand decreases.
- There is no need for separate manual configuration management for each application or usage.
In a typical IaaS cloud service, though the computing resources and infrastructure are provided as needed, the customer (developer) has to do all of the packaging and deployment of the application.
PaaS refers to the processing the packaging, deployment, and execution of the application ‘on its own’ on the cloud. If IaaS represents an early-stage cloud service, PaaS can be seen as the following advanced cloud service. The strength of using PaaS is that you can deploy and operate applications without any specialized knowledge or experience in allocating computing resources and deploying and running applications.
In particular, it is possible to scale up and down by increasing the distribution scale when the application demand increases and withdrawing the distribution when the application demand decreases. This means that there is no need for separate manual configuration management for each specific application or usage. This is consistent with the goal of Cloud Native Computing.
The key to cloud native computing is containerization. According to a 2020 survey of enterprise IT leaders, 85% said going cloud native is a high priority, and 86% are containerizing more applications. In another survey, when asked whether they use Kubernetes for container orchestration, 91% said yes. In the same survey, 75% said they already use Kubernetes in production.
Kubernetes’ status as a cloud native platform continues to grow, as discussed above. Application containerization is not an option, but a necessity, and Kubernetes adoption are overwhelming the container orchestration market. It seems that ‘Kubernetes’ is considered as a standard cloud operating system.
Eventually, Kubernetes will be able to replace the existing IaaS/hyperscaler layer completely.
Kubernetes management skills are complex, and the associated labor costs are high. It is tough if you write the YAML configuration file yourself.
In the future, the need to secure a scalable system and optimize the infrastructure cost and PaaS platform with the server’s stability will continue to come out. The container-based platform cocktail cloud of NAMUTECH, which is already in service in Korea, will continue to develop, and many companies will change to container-based.