We continue with the essay on comparison of Kubernetes with platform as a service framework. PaaS may be called out as being restrictive to applications, dictating choice of application frameworks, restricting supported language runtimes and distinguishing apps from services. Kubernetes, on the other hand, aims to support an extremely diverse variety of workloads. As long as the application has been compiled to run in a container, it will work with Kubernetes. Kubernetes evolved as an industry effort from the native Linux containers support of the operating system. It can be considered as a step towards a truly container centric development environment. Containers decouple applications from infrastructure which separates dev from ops.
Containers made PaaS possible. Containers help compile the code for isolation. PaaS enables applications and containers to run independently. PaaS containers were not open source. They were just proprietary to PaaS. This changed the model towards development centric container frameworks where applications could now be written with their own .
. Docker and Kubernetes fueled this move towards custom containers.Many people consider PaaS platform to be fixed and Container framework to be flexible. This is actually a shifting boundary between dev ops and developers
Many people consider PaaS platform to be fixed and Container framework to be flexible. This is actually a shifting boundary between dev ops and developers.
Platform-as-a-service was formed as an abstraction over cloud service providers. Container as a service was formed for the convenience of cloud workloads. Applications written in container frameworks can be moved around from cloud to cloud. For example, a Kubernetes application can be run in different clouds.
Containers made it possible for apps to run anywhere without any virtualization layer or middleware. Container frameworks only increased the coverage to span different systems. Container images also became open source. This made it easier for developers to move from PaaS to container frameworks. It is expected that nearly seventy percent of cloud workloads will run on containers.
In such case what is the future of PaaS?
Containers still need to be managed, deployed and monitored. This is where PaaS is helpful.
One of the improvements we could see going forward is containers dedicated for these purposes in a side-car model of deployment so that apps can focus on their logic while having aa set of sidecars automatically bringing the benefits of PaaS to container framework. Cert-managers and logging sidecars are an example of this.
Containers made PaaS possible. Containers help compile the code for isolation. PaaS enables applications and containers to run independently. PaaS containers were not open source. They were just proprietary to PaaS. This changed the model towards development centric container frameworks where applications could now be written with their own .
. Docker and Kubernetes fueled this move towards custom containers.Many people consider PaaS platform to be fixed and Container framework to be flexible. This is actually a shifting boundary between dev ops and developers
Many people consider PaaS platform to be fixed and Container framework to be flexible. This is actually a shifting boundary between dev ops and developers.
Platform-as-a-service was formed as an abstraction over cloud service providers. Container as a service was formed for the convenience of cloud workloads. Applications written in container frameworks can be moved around from cloud to cloud. For example, a Kubernetes application can be run in different clouds.
Containers made it possible for apps to run anywhere without any virtualization layer or middleware. Container frameworks only increased the coverage to span different systems. Container images also became open source. This made it easier for developers to move from PaaS to container frameworks. It is expected that nearly seventy percent of cloud workloads will run on containers.
In such case what is the future of PaaS?
Containers still need to be managed, deployed and monitored. This is where PaaS is helpful.
One of the improvements we could see going forward is containers dedicated for these purposes in a side-car model of deployment so that apps can focus on their logic while having aa set of sidecars automatically bringing the benefits of PaaS to container framework. Cert-managers and logging sidecars are an example of this.
No comments:
Post a Comment