![\"Docker](\"http:\/\/www.ghosh.com\/blog\/wp-content\/uploads\/2015\/03\/Docker-trends.png\")
<\/a><\/p>\nGoogle Trends - March 5, 2015<\/pre>\nSo, why is Docker so hot?<\/h1>\n
Software used to have a major delivery drag \u2013 it had to be delivered on some physical medium like tape, disk or download and then installed. Since software could only be consumed so quickly, the impetus of independent software vendors (ISVs) to build and deliver new software was perhaps at an annual or semi-annual basis. SaaS has changed all of that. Now, there\u2019s no reason why a bug cannot be fixed and delivered…instantly, or at least as \u201cfast as possible.\u201d<\/p>\n
Web scale SaaS companies (a la Facebook, Netflix, and a big slew of smaller SaaS companies) have been striving to optimize their software release stream to do just that. These modern ISVs have given rise to \u201cDevOps\u201d teams that focus on this task of \u201cContinuous Delivery\u201d. This has given rise to scripting technologies like Puppet and Chef for automating release cycles.<\/p>\n
The problem with these approaches is they are still prone to error. Creating a test environment via scripts is not 100% guaranteed to build an exact replica of the development environment, for example. So when QA finds a bug that is not reproducible in the development environment, valuable time is wasted determining if the bug is in the software or the environments.<\/p>\n
Docker changes this paradigm. Instead of pulling your hair out to recreate \u201cidentical\u201d environments, Docker gets much closer to actually just moving the actual environment around. This eliminates the errors due to release environment differences and the need to build and maintain lots of complex scripts.<\/p>\n
Docker provides additional benefits to SaaS ISVs as well. Docker is very light weight, and fast, which makes it easy to scale, resource efficient, and for new cloud ISVs that may not be invested in technology like VMware, Docker providers many of the classic benefits of virtualization.<\/p>\n
Enterprises need\u00a0Docker too<\/h1>\n
Understandably, large scale SaaS ISVs lead the way in innovation, including Docker implementation. Enterprise developers learn from these best practices and are starting to adopt Docker. Enterprises, too, benefit from the speed and efficiency of continuous delivery (CD), especially those enterprises building customer-facing scaled SaaS applications. But there\u2019s an even larger number of internal applications that perhaps don\u2019t need the daily updates, but certainly need greater efficiency delivered by Docker on internal teams with limited resources.<\/p>\n
What enterprise IT may not realize is that if they do not provide Docker for their developers, their developers have numerous external choices now for public hosted Docker services. In many cases, IT does not want their apps, workloads and data running on unsanctioned services, and the real problem is they probably won\u2019t know it\u2019s happening until well after the fact.<\/p>\n
Forward thinking IT are providing Docker for their developers, and those furthest along are discovering additional benefits of Docker ranging from lower costs via greater resource utilization or reduced VMware licensing costs to workload portability for moving apps to\/from public and private cloud infrastructures.<\/p>\n
But it ain\u2019t quite that simple<\/h1>\n
But what enterprise IT departments are also realizing is that Docker is not so simple to implement, especially given the unique needs of an enterprise. Docker is not an out of the box solution. To implement Docker, you must not only manage containers and orchestration, but ensure resource isolation and access control for security; streamline diverse stack support and upgrades; optimize data snapshotting, backups and recovery; implement monitoring at machine, instance, container and workload levels; and integrate with existing systems like LDAP or Active Directory.<\/p>\n
SaaS ISVs need to scale a single application, on a single app stack, on a single infrastructure, and they have engineering resources dedicated to implementing Docker and all requisite components. Enterprises, on the other hand, have diverse workloads, varied app stacks, heterogeneous infrastructures, limited resources, and additional needs for security, control, visibility, governance and compliance, so implementing all of the Docker related technologies for these permutations can be daunting.<\/p>\n
That\u2019s were PaaS comes in. A Docker-optimized PaaS for enterprise should take care of implementing Docker and required components, while meeting additional needs like role based access control based on existing IDM with visibility and monitoring. A well designed PaaS will also leverage the unique advantages of Docker to deliver features like idle workload hibernation for further infrastructure cost savings.<\/p>\n
Docker is young in the timeline of enterprise technology, but we\u2019ve rarely seen one grow and rise so quickly. Enterprises will lag slightly behind SaaS ISVs in Docker adoption, but the smart IT organizations will not only provide Docker to their developers before they wander elsewhere, but will also discover the other powerful advantages of Docker unique to enterprises without spending an arm and a leg.<\/p>\n","protected":false},"excerpt":{"rendered":"