The Virtualization Practice

Author Archive for Mike Kavis

Mike Kavis
Mike KavisMike is a VP/Principal Architect for Cloud Technology Partners. Mike has served in numerous technical roles such as CTO, Chief Architect, and VP positions with over 25 years of experience in software development and architecture. A pioneer in cloud computing, Mike led a team that built the world's first high speed transaction network in Amazon's public cloud and won the 2010 AWS Global Startup Challenge. An expert in cloud security, Mike is currently writing a book for Wiley Publishing called "Architecting the Cloud: Design Decisions for Cloud Computing Service Models (IaaS, PaaS, SaaS)" which is expected to be released in late 2013.

agilecloud

By now, we have all heard the success stories in which companies have increased their agility, lowered costs, reduced their data center footprint, built impressive high-scale systems, or gained competitive advantages by leveraging cloud computing services. But for every success story, there are one too many companies that struggle to capitalize on the promise of…

re-invent

This week, Amazon Web Services (AWS) held its second annual re:Invent conference. For the past two days, Amazon has been announcing a wide variety of feature enhancements to existing services as well as publicizing new services. Even before these announcements, AWS was so far ahead of their competition in features, customers, and rate of innovation that comparing competitors’ offerings to AWS was almost comical.

Codeship

Yesterday I had a chat with the folks at Codeship, a continuous integration and continuous deployment platform. The topic of immutable infrastructure came up and was intriguing to me, so I thought I would write about it. So what is immutable infrastructure? The concept of immutable infrastructure is to never change your existing production servers. Instead, build new automated servers and destroy the old. This concept falls in line with the “fail forward” belief system of many modern-day DevOps evangelists who believe that tweaking servers or rolling back code from servers in highly distributed systems is too risky and causes more problems than it is worth.

agilecloud

Many companies use some flavor of an agile methodology today with mixed results. I have written about agile fail patterns in the past, but some companies do an excellent job of applying agile best practices yet still suffer from missed dates, botched deployments, and low quality. Why is that, you may ask? Because most agile methodologies only address the development side of the house and clearly ignore the operations side of the house. The two need to work in tandem to produce the desired results, which is the goal of DevOps.

Google Circle
Join my Circle on Google+

Plugin by Social Author Bio