Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

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
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
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...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up 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.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.