{"id":21621,"date":"2016-04-06T14:53:58","date_gmt":"2016-04-06T14:53:58","guid":{"rendered":"http:\/\/www.businesscloudnews.com\/?p=248612"},"modified":"2016-04-06T14:53:58","modified_gmt":"2016-04-06T14:53:58","slug":"will-containers-change-the-world-of-cloud","status":"publish","type":"post","link":"https:\/\/icloud.pe\/blog\/will-containers-change-the-world-of-cloud\/","title":{"rendered":"Will containers change the world of cloud?"},"content":{"rendered":"

\"Global<\/a>The rise of containers as a technology has been glorious and confusing in equal measure. While touted by some as the saviour of developers, and by others as the end of VM\u2019s, the majority simply don\u2019t understand containers as a concept or a technology.<\/p>\n

In the simplest of terms, containers let you pack more computing workloads onto a single server and in theory, that means you can buy less hardware, build or rent less data centre space, and hire fewer people to manage that equipment.<\/p>\n

\u201cIn the earlier years of computing, we had dedicated servers which later evolved with virtualisation,\u201d say Giri Fox, Director of Technical Services at Rackspace. \u201cContainers are part of the next evolution of servers, and have gained large media and technologist attention. In essence, containers are the lightest way to define an application and to transport it between servers. They enable an application to be sliced into small elements and distributed on one or more servers, which in turn improves resource usage and can even reduce costs.\u201d<\/p>\n

There are some clear differences between containers and virtual machines though. Linux containers give each application, its own isolated environment in which to run, but multiple containers share the host servers\u2019 operating system. Since you don\u2019t have to boot up an operating system, you can create containers in seconds not minutes like virtual machines. They are faster, require less memory space, offer higher-level isolation and are highly portable.<\/p>\n

\u201cContainers are more responsive and can run the same task faster,\u201d adds Fox. \u201cThey increase the velocity of application development, and can make continuous integration and deployment easier. They often offer reduced costs for IT; testing and production environments can be smaller than without containers. Plus, the density of applications on a server can be increased which leads to better utilisation.<\/p>\n

\u201cAs a direct result of these two benefits, the scope for innovation is greater than its previous technologies. This can facilitate application modernisation and allow more room to experiment.\u201d<\/p>\n

So the benefits are pretty open-ended. Speed of deployment, flexibility to run anywhere, no more expensive licenses, more reliable and more opportunity for innovation.<\/p>\n

Which all sounds great, doesn\u2019t it?<\/p>\n

\"Capture\"<\/a>That said, a recent survey<\/a> from the Cloud & DevOps World team brought out some very interesting statistics, first and foremost the understanding of the technology. 76% of respondents agreed with the statement \u201cEveryone has heard of containers, but no-one really understands what containers are\u201d.<\/p>\n

While containers have the potential to be
\nthe next big thing in the cloud industry, unless those in the ecosystem understand the concept and perceived benefits, it is unlikely to take off.<\/p>\n

\u201cContainers are evolving rapidly and present an interesting runtime option for application development,\u201d says Joe Pynadath, \u200eGM of EMEA for Chef. \u201cWe know that with today\u2019s distributed and lightweight apps, businesses, whether they are a new start-up\u2019s to traditional enterprise, must accelerate their capabilities for building, testing, and delivering modern applications that drive revenue.<\/p>\n

\u201cOne result of the ever-greater focus on software development is the use of new tools to build applications more rapidly and it is here that containers have emerged as an interesting route for developers. This is because they allow you to quickly build applications in a portable and lightweight manner. This provides a huge benefit for developers in speeding up the application building process. However, despite this, containers are not able to solve the complexities of taking an application from build through test to production, which presents a range of management challenges for developers and operations engineers looking to use them.\u201d<\/p>\n

There is certainly potential for containers within the enterprise environment, but as with all emerging technologies there is a certain level of confusion as to how they will integrate within the current business model, and how the introduction will impact the IT department on a day-to-day basis.<\/p>\n

\u201cSome of the questions we\u2019re regularly asked by businesses looking to use containers are \u201cHow do you configure and tune the OS that will host them? How do you adapt your containers at run time to the needs of the dev, test and production environments they’re in?\u201d comments Pynadath.<\/p>\n

While containers allow you to use discovery services or roll your own solutions, the need to monitor and manage them in an automated way remains a challenge for IT teams. At Chef, we understand the benefits containers can bring to developers and are excited to help them automate many of the complex elements that are necessary to support containerized workflows in production\u201d<\/p>\n

Vendors are confident that the introduction of containers will drive further efficiencies and speed within the industry, though we\u2019re yet to see a firm commitment from the mass market to demonstrate the technology will take off. The early adopter uptake is promising, and there are case studies to demonstrate the much lauded potential, but it\u2019s still early days.<\/p>\n

In short, containers are good, but most people just need to learn what they are.<\/p>\n","protected":false},"excerpt":{"rendered":"

The rise of containers as a technology has been glorious and confusing in equal measure. While touted by some as the saviour of developers, and by others as the end of VM’s, the majority simply don’t understand containers as a concept or a technology.<\/p>\n","protected":false},"author":203,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1472,2061,1990,443],"tags":[],"class_list":["post-21621","post","type-post","status-publish","format-standard","hentry","category-chef","category-containers","category-features","category-rackspace"],"_links":{"self":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/21621","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/users\/203"}],"replies":[{"embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/comments?post=21621"}],"version-history":[{"count":1,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/21621\/revisions"}],"predecessor-version":[{"id":21622,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/21621\/revisions\/21622"}],"wp:attachment":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/media?parent=21621"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/categories?post=21621"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/tags?post=21621"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}