December 25, 2015 at 12:26A little bit about working with containers
- Transfer
The other day we wrote about which products in this area were introduced by VMware, and today we decided to talk about the general impression shared by experts regarding container technology.
/ Photo by Bernard Spragg. NZ / PD
Many people call container technology an IT revolution. Major players and leaders in virtualization such as VMware could not even afford a hint of lagging behind market expectations and followed the trend set by Docker.
At specialized conferences, experts are trying to solve the problem, which lies in the growing gap between developers who prefer Docker because of its convenience, and IT companies that set their goals and prefer the classic approach.
VMware offers a range of solutions to bridge the gap between the first and second. Of course, this is not so easy due to the general management difficulties that are present in almost every IT company that is trying to keep up with the trends.
This technology allows containers to be attached to processes, which differs from how virtual machines work that provide isolation at the hardware level. In the case of containers, this is not possible.
It requires a completely different approach to application architecture. A good example would be to study our material on how to scale Ruby applications. It summarizes how Dyno containers work on Heroku. As a result, we can say that to fully work with containers, it is necessary to use new technologies, protocols, gateways and schedulers.
As with the scaling example, you should understand the overall load of your product or service in order to assess the need for containers. If you are just starting out or working with a service that does not require the implementation of DevOps technologies, you can relax.
Containers are not for everyone. If your processes are already optimized and you use relatively new tools in working with virtual machines, then you should seriously realize that there is no need to switch to something like Docker.
In this case, all your best practices for monitoring, deploying and managing service services will not turn into empty projects, the time for which was wasted. Only a small part of all this can be used in a container environment.
One way or another, experiments with new technologies have not hurt anyone. Here you have a great opportunity to develop open source projects that will help the whole community and allow you to demonstrate your level of knowledge and experience.
Well, if you think about a smooth transition to containers, the new products from VMware, which we talked about earlier , will come in handy .
PS Other materials on containers and virtualization on 1cloud's blog:
VMware offers a range of solutions to bridge the gap between the first and second. Of course, this is not so easy due to the general management difficulties that are present in almost every IT company that is trying to keep up with the trends.
This technology allows containers to be attached to processes, which differs from how virtual machines work that provide isolation at the hardware level. In the case of containers, this is not possible.
It requires a completely different approach to application architecture. A good example would be to study our material on how to scale Ruby applications. It summarizes how Dyno containers work on Heroku. As a result, we can say that to fully work with containers, it is necessary to use new technologies, protocols, gateways and schedulers.
As with the scaling example, you should understand the overall load of your product or service in order to assess the need for containers. If you are just starting out or working with a service that does not require the implementation of DevOps technologies, you can relax.
Containers are not for everyone. If your processes are already optimized and you use relatively new tools in working with virtual machines, then you should seriously realize that there is no need to switch to something like Docker.
In this case, all your best practices for monitoring, deploying and managing service services will not turn into empty projects, the time for which was wasted. Only a small part of all this can be used in a container environment.
One way or another, experiments with new technologies have not hurt anyone. Here you have a great opportunity to develop open source projects that will help the whole community and allow you to demonstrate your level of knowledge and experience.
Well, if you think about a smooth transition to containers, the new products from VMware, which we talked about earlier , will come in handy .
PS Other materials on containers and virtualization on 1cloud's blog: