Welcome!

Microservices Expo Authors: Liz McMillan, Elizabeth White, Charles Araujo, Pat Romanski, Flint Brenton

Related Topics: @DevOpsSummit, Microservices Expo, Linux Containers, Open Source Cloud, Containers Expo Blog, @CloudExpo

@DevOpsSummit: Blog Post

Why Docker Is Not Enough By @Bart_Copeland | @DevOpsSummit @ActiveState #DevOps #Docker #Containers #Microservices

It's important to weigh all the issues and understand how Docker will meet the needs of the enterprise as a whole

Why Docker Is Not Enough for Enterprise IT

I want to start by saying that, at ActiveState, we absolutely love Docker. We think it's phenomenal technology that is really becoming the global currency of the cloud. We've written about Docker a lot on the ActiveState blog - we've celebrated its birthday, discussed evolving technologies surrounding it, and shown how we've integrated Docker into Stackato. But, I wanted to share with you why we feel Docker alone is not enough for the enterprise.

Two Major Issues Faced by Enterprise IT
First, I'm going to discuss two underlying problems that plague most enterprises today:

  1. Shipping Code Is Hard
    Shipping code can be really hard. The reason? There's no simple way to package your application code, complete with your system dependencies. You are dealing with code across different operating systems, different hypervisors or different infrastructures-as-a-service. That is a real challenge in shipping software.
  2. Devs and Ops Don't Always Play Well Together
    Another common issue that enterprises must deal with is the challenge of handing off code from developers to operations teams. There isn't necessarily a harmonious relationship that exists between these two constituents. And often there's a lot of tension.

It Starts with Docker
Docker has been very appealing to people because it seems to solve these problems. The first problem appears to be fixed because you're able to package up everything related to your app into a single application process.

The second problem seems to be solved because there is a clean separation between IT ops and developers. Developers worry about what goes inside the Docker container and IT ops worries about what goes on outside the container. This makes it more convenient--the developer can provide the container (and whatever is inside) to IT ops and then they can run with it. Now, it's a very portable solution.

However, Docker only partially solves these problems.

What Is Docker Missing?
We're all familiar with Lego bricks. They're a very powerful creative toy for children and even some adults. Think of a Docker container as Lego, with each individual brick representing a Docker container. Now the beauty of Lego is that you can assemble the bricks and build all sorts of amazing things. Same thing applies to Docker containers. However, with Docker, issues such as orchestration, monitoring, logging, and scaling become a concern for enterprises. A Docker container is fine for a start-up or a small company if it's only running a handful of containers, but what if you're running hundreds or thousands of Docker containers? These are just some of the issues that need to be considered which are above and beyond what the Docker container itself can provide, and why Docker wouldn't be enough.

So let's go through some specific areas in which containers, by themselves, fall short:

Loading the Container
The first problem is loading the container. How does a developer get its application into the container? And there's also the burden of building Docker images for the developer. The developer needs to be focused on the code, not on the various system dependencies. The solution for this is something we call Buildpacks. Buildpacks were revolutionized by a company named Heroku, which is one of the first companies in the Platform-as-a-Service (PaaS) space. We at ActiveState adopted Cloud Foundry v1 and then incorporated buildpacks. Cloud Foundry then also adopted Buildpacks in version 2 of the project. Buildpacks are the best and most portable option for PaaS, and the majority of the PaaS ecosystem is standardizing on them. They allow you to build up your stack, including all the system dependencies inside the container, as well as configure your application's environment. Developers just need to supply and think about their application code. They don't have to worry about anything else. Buildpacks configure your application.

Shipping the Container
What happens when all of a sudden developers throw a whole bunch of Docker containers at IT ops and say, "Ship these. Deploy these to production." How does IT ops ship these containers in a systematic way to manage performance, manage security, and manage compliance? They have all these Lego bricks. How do they manage these Lego bricks? So how do you ship the container? The answer to that is something called Docker Schedulers. There are a number of schedulers in the marketplace today: Google Kubernetes, Apache Mesos; Cloud Foundry Diego; CoreOS and then there's Stackato, our enterprise private Cloud Foundry solution that allows you to schedule your Docker containers. The scheduler orchestrates and runs the containers for you, and distributes them across your cluster, whatever your Cloud cluster is. It's resilient, so if a container or machine or application goes down it redistributes those containers elsewhere. From the end user's perspective there's no downtime. While these schedulers are helpful in solving part of the shipping problem, there are still another important issue that enterprises face that a scheduler can't solve.

Bridging the Divide with Developer Self-Service
There's another key aspect, and this is more cultural, that exists within enterprises. That is this divide that exists between developers and IT ops. Right now there is some classic tension that exists between these two organizations. In some respects you can say there is a wall between them. Often what happens is a developer will build an application and then throw it over the wall to IT ops. Most of the time they end up with an application that doesn't work. As a result, deploying an application to production in an enterprise takes literally weeks or months to do. It's not uncommon to hear how frustrating and how long it takes for developers to deploy applications in production.

Some of this cultural divide exists with infrastructure. Because the enterprise is still using an outdated ticketing system to get access to virtual machines, access to compute cycles can take weeks when it should be literally minutes.

In order to break down this wall, there needs to be a way in which developers can do it themselves. We need tools that empower developers. They need to be able to self-serve in a way that works for the enterprise. Give the developer freedom to deploy on his own, but also address security and compliance needs of the enterprise as well as managing multi-tenancy. The developer only thinks about his or her single app, but the enterprise needs to think about all of the apps that are being submitted by various developers. How do you deal with this? How do you break down this wall that exists between developers and IT ops? The answer is PaaS. With PaaS you have a platform that sits between your applications and your infrastructure. This platform is the same one that goes from development to QA to staging and to production, giving a seamless application delivery experience. The developer who is building an application is doing it in such a way when it's ready, they pass it to QA and it works. They're no longer throwing it over the wall - they know it's going to work because everybody is using the same platform.

Conclusion
There are a lot of people collaborating around Docker and we, at ActiveState, fundamentally believe that Docker is the future. When we were building Stackato v3.0 we said we needed to have Docker in it, and we have recently expanded the functionality so users can deploy their Docker apps to Stackato. But there are limitations for the enterprise because it needs a solution above and beyond containers. With more than 70% of people saying they are actively evaluating or using Docker, it's important to weigh all the issues and understand how Docker will meet the needs of the enterprise as a whole.

The post Why Docker Is Not Enough for Enterprise IT appeared first on ActiveState.

More Stories By Bart Copeland

As President & CEO of ActiveState Software, Bart Copeland brings more than twenty years of management, finance, and technology business experience to his role. With a passion for technologies that help people lead more productive and enjoyable lives, Bart is currently focused on ActiveState’s private platform-as-a-service (PaaS) offering, Stackato. With his vision for PaaS as an enabler to accelerate cloud adoption and value in enterprises, Bart is actively involved in the strategy, roadmap, business development and evangelism of Stackato. Bart is also an active angel investor and serves as a director on a number of other tech companies. He holds an MBA in Technology Management from the University of Phoenix and a Mechanical Engineering degree from the University of British Columbia.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his general session at @DevOpsSummit at 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, will discuss how customers are able to achieve a level of transparency that e...
The Jevons Paradox suggests that when technological advances increase efficiency of a resource, it results in an overall increase in consumption. Writing on the increased use of coal as a result of technological improvements, 19th-century economist William Stanley Jevons found that these improvements led to the development of new ways to utilize coal. In his session at 19th Cloud Expo, Mark Thiele, Chief Strategy Officer for Apcera, compared the Jevons Paradox to modern-day enterprise IT, examin...
The taxi industry never saw Uber coming. Startups are a threat to incumbents like never before, and a major enabler for startups is that they are instantly “cloud ready.” If innovation moves at the pace of IT, then your company is in trouble. Why? Because your data center will not keep up with frenetic pace AWS, Microsoft and Google are rolling out new capabilities. In his session at 20th Cloud Expo, Don Browning, VP of Cloud Architecture at Turner, posited that disruption is inevitable for comp...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
Your homes and cars can be automated and self-serviced. Why can't your storage? From simply asking questions to analyze and troubleshoot your infrastructure, to provisioning storage with snapshots, recovery and replication, your wildest sci-fi dream has come true. In his session at @DevOpsSummit at 20th Cloud Expo, Dan Florea, Director of Product Management at Tintri, provided a ChatOps demo where you can talk to your storage and manage it from anywhere, through Slack and similar services with...
Containers are rapidly finding their way into enterprise data centers, but change is difficult. How do enterprises transform their architecture with technologies like containers without losing the reliable components of their current solutions? In his session at @DevOpsSummit at 21st Cloud Expo, Tony Campbell, Director, Educational Services at CoreOS, will explore the challenges organizations are facing today as they move to containers and go over how Kubernetes applications can deploy with lega...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
Learn how to solve the problem of keeping files in sync between multiple Docker containers. In his session at 16th Cloud Expo, Aaron Brongersma, Senior Infrastructure Engineer at Modulus, discussed using rsync, GlusterFS, EBS and Bit Torrent Sync. He broke down the tools that are needed to help create a seamless user experience. In the end, can we have an environment where we can easily move Docker containers, servers, and volumes without impacting our applications? He shared his results so yo...
Don’t go chasing waterfall … development, that is. According to a recent post by Madison Moore on Medium featuring insights from several software delivery industry leaders, waterfall is – while still popular – not the best way to win in the marketplace. With methodologies like Agile, DevOps and Continuous Delivery becoming ever more prominent over the past 15 years or so, waterfall is old news. Or, is it? Moore cites a recent study by Gartner: “According to Gartner’s IT Key Metrics Data report, ...
Kubernetes is a new and revolutionary open-sourced system for managing containers across multiple hosts in a cluster. Ansible is a simple IT automation tool for just about any requirement for reproducible environments. In his session at @DevOpsSummit at 18th Cloud Expo, Patrick Galbraith, a principal engineer at HPE, discussed how to build a fully functional Kubernetes cluster on a number of virtual machines or bare-metal hosts. Also included will be a brief demonstration of running a Galera MyS...
Enterprise architects are increasingly adopting multi-cloud strategies as they seek to utilize existing data center assets, leverage the advantages of cloud computing and avoid cloud vendor lock-in. This requires a globally aware traffic management strategy that can monitor infrastructure health across data centers and end-user experience globally, while responding to control changes and system specification at the speed of today’s DevOps teams. In his session at 20th Cloud Expo, Josh Gray, Chie...
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
In IT, we sometimes coin terms for things before we know exactly what they are and how they’ll be used. The resulting terms may capture a common set of aspirations and goals – as “cloud” did broadly for on-demand, self-service, and flexible computing. But such a term can also lump together diverse and even competing practices, technologies, and priorities to the point where important distinctions are glossed over and lost.
"I will be talking about ChatOps and ChatOps as a way to solve some problems in the DevOps space," explained Himanshu Chhetri, CTO of Addteq, in this SYS-CON.tv interview at @DevOpsSummit at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
For organizations that have amassed large sums of software complexity, taking a microservices approach is the first step toward DevOps and continuous improvement / development. Integrating system-level analysis with microservices makes it easier to change and add functionality to applications at any time without the increase of risk. Before you start big transformation projects or a cloud migration, make sure these changes won’t take down your entire organization.
When you focus on a journey from up-close, you look at your own technical and cultural history and how you changed it for the benefit of the customer. This was our starting point: too many integration issues, 13 SWP days and very long cycles. It was evident that in this fast-paced industry we could no longer afford this reality. We needed something that would take us beyond reducing the development lifecycles, CI and Agile methodologies. We made a fundamental difference, even changed our culture...
High-velocity engineering teams are applying not only continuous delivery processes, but also lessons in experimentation from established leaders like Amazon, Netflix, and Facebook. These companies have made experimentation a foundation for their release processes, allowing them to try out major feature releases and redesigns within smaller groups before making them broadly available. In his session at 21st Cloud Expo, Brian Lucas, Senior Staff Engineer at Optimizely, discussed how by using ne...