We all need performance and capacity management tools to fine tune our virtual and cloud environments, but we need them to do more than just tell us there may be problems. Instead, we need them to find root causes for problems, whether those problems are related to code, infrastructure, or security. The new brand of applications, if designed for the cloud à la Netflix, or older technologies instantiated within the cloud need more in order to tell us about their health. Into this breach comes a new set of tools, as well as an existing set of tools.
With the proliferation of virtualized applications and desktops, the concept of any user accessing any application or desktop from any device has become reality. Whether accessed from a smartphone, tablet, or desktop, whether tethered or untethered, all the resources that users require must be accessible.
I agree that containers will be the future of computing. However, that may not happen anytime soon. Containers have many hurdles to get over before they can take over the world. Some of these hurdles are related to politics within organizations, and others are technical. Let me discuss the technical ones.
The latest and greatest thing in the data center is apparently containers. For those of us with long enough teeth to remember the heady days of the early millennium, they look and smell a lot like Solaris Zones.
Containers in their current incarnations are garnering a great deal of attention, especially in the DevOps world, where continuous deployment is the latest word in deployment strategies.
It is said that nothing is new in the world, and with containers, this statement could not be truer. I think, therefore, that an overview of the evolution of the container may be useful.
One of the key features of a hyperconverged infrastructure (HCI) solution is appliance-based scale-out architecture. A workload is housed on a collection of these appliances, which are the standard building blocks. The number of blocks is selected to deliver sufficient resources for the workload. But just how standard are these building blocks? Over time, I’ve seen HCI vendors offering quite a bit of variation across their models. Does this reduce or negate the value of the scale-out nature of hyperconverged?
SaaS is supposed to be ubiquitous, and never go down. But what if the SaaS you are using suddenly goes away, closes up shop, or places the part you are using in an unsupported mode? For some SaaS offerings (such as a game) this may not be a big deal, but for others (such as a CRM) it has huge consequences—ones that can affect your business in subtle and major ways.