Containerization - new shared-hosting
New solutions for virtualization and containerization are used by developers to test applications and support the development infrastructure. But will it be a new shared-hosting format?
')
As a solution, it suggests the possibility of taking advantage of containerization. Currently technologies are ready for industrial use:
Containers as the basis for shared hosting are profitable for the hosters themselves. You can serve as a traditional hosting and as a cloud, PaaS, SaaS, and so on, depending on what is at the top of the news. For example, today it is Docker, which is actively developing by the community.
Using containers that are the same on the user's machine and on the hosting reduces the chain from deciding to create a website to directly launching the application on the hosting and simplifies the deployment and transfer of the application to the new hosting. To deploy a site or application, it is enough to provide a text description file of the container and enter credit card information. It is definitely easier than uploading files via FTP.
The user is tied to the company, because it is technically possible to provide scaling to a greater extent than before. To temporarily solve performance problems, it is sufficient to transfer the container to a less loaded node. Thanks to CRIU, in most cases this will happen transparently to the user.
There is an opportunity to reduce the number of cars. Containers can be added to both idle servers and part-time servers. There is an opportunity to quickly put into operation and decommission physical servers. It becomes possible to dispose of unused computing resources by other non-shared hosting applications.
Finally, the question to the community is whether a more technological platform is the decisive factor in the choice of hosting, or does support and marketing decide everything?
What I see in shared hosting today
- Customers want less technical details and store everything in the “cloud”
- Compared to what was five years ago, you need less magic actions in the unix shell to launch your application (panels appeared, containers, simple installers)
- There are many SaaS and PaaS applications that perform all the same functions as self-hosted applications.
')
As a solution, it suggests the possibility of taking advantage of containerization. Currently technologies are ready for industrial use:
- Maas / juju - Ubuntu stack, allows you to manage a variety of geographically distributed physical servers and run applications from pre-built templates.
- Proprietary clouds: Red Hat (OpenShift), VMWare (Cloud Foundry), Google (App Engine)
- Modern solutions for shared hosting (CloudLinux with isolated environments)
- Docker: solves the problem of delivering an application from a client to a hosting platform and generally changes the paradigm from “client / site” to “client / application”, which brings hosting closer to business. Docker allows you to use LXC containers. CRIU (OpenVZ / Parallels) allows you to transfer LXC containers between physical machines transparently to the user.
What we get as a result?
Containers as the basis for shared hosting are profitable for the hosters themselves. You can serve as a traditional hosting and as a cloud, PaaS, SaaS, and so on, depending on what is at the top of the news. For example, today it is Docker, which is actively developing by the community.
Using containers that are the same on the user's machine and on the hosting reduces the chain from deciding to create a website to directly launching the application on the hosting and simplifies the deployment and transfer of the application to the new hosting. To deploy a site or application, it is enough to provide a text description file of the container and enter credit card information. It is definitely easier than uploading files via FTP.
The user is tied to the company, because it is technically possible to provide scaling to a greater extent than before. To temporarily solve performance problems, it is sufficient to transfer the container to a less loaded node. Thanks to CRIU, in most cases this will happen transparently to the user.
There is an opportunity to reduce the number of cars. Containers can be added to both idle servers and part-time servers. There is an opportunity to quickly put into operation and decommission physical servers. It becomes possible to dispose of unused computing resources by other non-shared hosting applications.
Finally, the question to the community is whether a more technological platform is the decisive factor in the choice of hosting, or does support and marketing decide everything?
Source: https://habr.com/ru/post/235803/
All Articles