RightScale just published its annual report on the state of the cloud, and some of the key findings are very interesting. Topics range from cloud vendor market share to cloud adoption concerns, DevOps tools adoption, public vs. private cloud adoption, and much more. Below, I highlight the major findings I thought most interesting and follow each with my perspective on it.
Transformation & Agility
Transformation & Agility concerns the utilization of the technical agility derived from the benefits delivered by virtualization and cloud computing, coupled with Agile Development practices that improve business agility, performance, and results. This includes the agility derived from: (Read More)
- The implementation of Agile and DevOps methodologies
- The application and system architectures
- The implementation of IaaS, PaaS, and SaaS clouds
- Monitoring of the environment, coupled with processes for resolving problems quickly
- Having continuous availability through the use of high-availability and disaster recovery products and procedures
Transformation covers the journey from A to Z and all points between: how you get there and the roads you will travel; how decisions made on day zero or one, or even day three, will affect later decisions; and what technical, operational, and organizational pitfalls can be associated with an implementation. We examine what tool sets are required for Agile Cloud Development, and it delves into other aspects of Agile Development that integrate with cloud computing, SaaS, and PaaS environments, including DevOps, Scrum, XP, and Kanban.
Over the past few months, I’ve been writing about my engagement with a global organization and its journey of transformation into a more agile organization, driving business enablement. One thing has remained missing: real leadership. This large corporation has thousands upon thousands of people, and many of them are in “leadership” roles. The problem here is that no one is ready to understand the underlying lessons at play or is able to apply those lessons to their own or their organization’s benefit.
There is a growing movement to encrypt everything. I prefer encrypting specific data, not everything. However, modern CPU chipset features have sped up encryption so much that encrypting everything is a valid option. Encryption requires one to have access to the keys or the related encryption secrets. Those secrets need to be at the fingertips of your applications or management tools. Encryption secrets should be readily available to an application. How do we achieve this? The February 9, 2017 Virtualization and Cloud Security Podcast addresses this issue. In this podcast, Virtuozzo’s Chief Software Architect, Pavel Emelyanov, joins us to discuss container encryption.
Will virtual reality have a place in IT? Virtual reality (VR) is still in its infancy, currently most associated with the computer gaming industry. However, there is strong interest in it from companies outside computer gaming. As a matter of fact, Mark Zuckerberg over at Facebook has been quite interested in using virtual reality to expand the Facebook platform. Some are predicting that 2017 will be the year when Facebook VR finally emerges.
There is a recent CVE (CVE-2016-9962) that directly affects container security. A patch was quickly forthcoming. This raised some interesting concerns. Specifically, how do you patch a container infrastructure? What needs to be patched? The “what” is easy; the “how” is more difficult. As we move to cloud-native applications, where we tear down apps rapidly and restart them from whole cloth, patching is a crucial issue. There is risk here; the question is how to mitigate such risk. How do you patch for future issues? This was the subject of the virtualization and cloud security podcast this week.
In IT there is not simply more than one way to skin a cat. There are multiple philosophies describing the methods. Most of these philosophies are based on preference and history, and on how, where, and when we learn, but not so much on what is necessarily the best way. Much of the how and when is linked to cycles that seem to permeate the industry: cycles of ideas that surface, are used, are bettered, and eventually resurface.