Monday, October 31, 2016

The blind adoption mistake: How to determine if containers are right for you [feedly]

The blind adoption mistake: How to determine if containers are right for you
// Chef Blog

Making mistakes is part of life. But that doesn't mean blindly making choices, in life, or in technology, without considering whether others have trodden the same path before. Every generation of technology — disruptive or not — brings with it a similar set of challenges as the previous generation, only in a different form. One of my colleagues in sales says, half-jokingly, that if you want to know where the next set of problems will come from with a new technology, pull out an architectural diagram of a 1960's mainframe. It provides a map for what part of the system needs to be built next. It's an apt comparison; after all, new technology is no panacea. It merely shifts the need for innovation to another area.

I remember when VMware and virtualization burst onto the scene in the late 90's. Back then, I was a systems administrator trying to modernize our data centers. My bosses fell in love with virtualization before anyone really understood best practices for this new technology, or who the standard-bearers in this new space would be. They insisted that we virtualize our servers at a ratio of 8-to-1, without understanding that following some figure on a vendor's data sheet did not equate to actual business value. Also, any company in business for more than a decade has a high level of heterogeneity in its IT infrastructure: mainframes, ancient UNIX servers, and desktops in the data center are embarrassing, but a reality. Imposing new technology as an all-in general practice ignores this fact.

Sweeping technology initiatives often fail to address the real question: what value will it deliver for our customers?

Understanding Containers' Value

A very similar form of technology myopia has descended on the marketplace today in containerization. Containers have startups, incumbent vendors, and end users in a frenzy, all espousing the technology as a one-size-fits-all panacea. But we don't yet know how containers' value proposition will ultimately be defined, or what solutions will win the day.

A recent Gartner report reinforces this skepticism, saying "Industry hype is excessive and is focused too narrowly on a handful of products in the container… market."

Companies need to consider the real value to customers when embarking on technology initiatives. Otherwise they are just cool, but often time- and money-wasting engineering projects. Gartner states, "Enterprises need to understand the capabilities of container orchestration tools, as well as how they fit into an overall data center tooling strategy, because container orchestration tooling alone will not support the production operationalization of containers at scale."

Five Ways to Avoid Mistakes of the Past

While container technology has been around for some time — and Docker certainly has made revolutionary inroads by making containers easy-to-use for the average developer — there are still a number of unknowns about this latest generation of technology. So let's learn from our predecessors in previous innovation cycles. Doing so will ensure we  avoid making the same mistakes as past generations when we adopt products from this one. Here are some tips to learn from the past:

  1. Analyze and understand the maturity level of your technology culture and infrastructure. An objective assessment of your people and systems' capabilities provides insight into whether or not adoption of a technology is right . Too many organizations attempt to embrace the latest innovation in cultures ill-equipped to make use of bleeding-edge technology.
  2. Be patient. It can take time for an emerging market for disruptive technology to figure itself out. Allow time for a few vendors to mature so you can be sure you're committed to the right players.
  3. Business and technology teams need to remain aligned in adoption decisions. There's no sense in rushing into a new technology with all the operational costs and upheaval it will entail without a clear, honest and realistic assessment of the business value it will provide.
  4. Use a healthy dose of open source with any new technology. Open source ensures flexibility as your business needs grow  and freedom to customize technology to meet your business needs without being locked into a specific vendor.
  5. Work with vendors who reflect your organization's own culture, values and strategic instincts. These partnership bonds are especially important when assessing a fledgling technology like today's containers, because there may be a slew of critical and collaborative adjustments down the road as the solution's highest and best use is determined.

How to Succeed with Containers

There is a strong business case for containers. But companies should ensure they have a high level of operational maturity, a culture of innovation, and an agile, DevOps-friendly environment to ensure success with container adoption.

Gartner suggests enterprises "capture and prioritize your container orchestration requirements, embed container deployment use case requirements in your overall data center architecture and scrutinize your organization's ability to deploy, integrate and support the requisite container-related tooling."

If your organization is considering containers, following these best practices will drive success and ensure you avoid the technology adoption mistakes that have plagued previous generations. Make sure you adopt containers in a way that delivers positive business outcomes, instead of creating yet another mess for your IT teams to clean up later.

DevOps Resources

The post The blind adoption mistake: How to determine if containers are right for you appeared first on Chef Blog.


Shared via my feedly newsfeed

Sent from my iPhone

No comments:

Post a Comment