1,734
edits
Changes
update scenarios
== Improved security CI/CD and development operations ==
== Server consolidation Containers and big data == Having a separate physical server for each application is generally a good approach, it increases availability and improves security. However, separate servers lead to increased costs of hardware and collocation, and modern hardware is often underutilized in this scenario. With OpenVZ, you can enjoy the benefits of dedicated server without such drawbacks. Create a container for each application and use the existing hardware more efficiently. This approach can be deployed totally transparently to users using OpenVZ.
== Hosting ==
* Much easier to administer
== Educational Server consolidation ==
== Small usecases See also ==
* [[Virtual HSMSuccess stories]] is a software suite for storing and manipulating secret data outside the virtualized application environment.* Docker containers are not safe from security point of view due to poor isolation[http://h20195.www2.hp.com/V2/getpdf.aspx/4AA5-9251ENW.pdf?ver=1. You can setup [[Docker inside CT|Docker inside OpenVZ]] [[0 Technical white paper: Linux containertechnology]] and it's containers there.