I've noticed a bit of a disturbing pattern of late in my cloud discussions with clients. They have been talking about hybrid cloud in the future tense. If you are planning for hybrid down the road, I have a wake up call for you. Too late, you are already hybrid.
If your company has even a single SaaS application in use today I can almost gurantee you it's connected to something inside your data center giving you hybrid cloud. So hybrid isn't a future state after you have a private cloud in place and IT Ops chooses to connect that private cloud to a public cloud. Look at it through the lens of a business process or application service which is composed of different components, some cloud-based, some on-premise. From an Infrastructure & Operations perspective, hybrid cloud means a cloud service connected to any other corporate resource (a back office app, your web site, your intranet, another SaaS app you have under contract and yes, even your private cloud). Any of these types of connections presents the same integration impact - whether you established the connection or not. If you are like the typical enterprise, that answered our Forrsights Q4 2012 Software Survey, then you have more than six SaaS applications in place today (that you know about) so cloud integration is likely well in place today. And about one third of the developers who responded to our Forrsights Q1 2013 Developer Survey said they have already deployed applications to the public cloud. Twenty-five percent also admitted to putting application integrations in place.
Hybrid clouds are especially subject to the law of unintended consequences, says Forrester’s cloud expert James Staten. Many IT organizations don’t even acknowledge that they have a hybrid cloud. The reality: If enterprises are using public cloud software-as-a-service (SaaS) and/or deploying any custom applications in the public cloud, then by definition they have a hybrid cloud, because it almost always connects to the back end.
In this episode of TechnoPolitics, James implores CIOs and IT professionals to get serious about hybrid cloud now to avoid spaghetti clouds in the future.
On Tuesday, September 4, Microsoft made the official announcement of Windows Server 2012, ending what has seemed like an interminable sequence of rumors, Beta releases, and endless speculation about this successor to Windows Server 2008.
So, is it worth the wait and does it live up to its hype? All omens point to a resounding “YES.”
Make no mistake, this is a really major restructuring of the OS, and a major step-function in capabilities aligned with several major strategic trends for both Microsoft and the rest of the industry. While Microsoft’s high level message is centered on the cloud, and on the Windows Server 2012 features that make it a productive platform upon which both enterprises and service providers can build a cost-effective cloud, its features will be immensely valuable to a wide range of businesses.
What It Does
The reviewers guide for Windows Server 2012 is over 220 pages long, and the OS has at least 100 features that are worth noting, so a real exploration of the features of this OS is way beyond what I can do here. Nonetheless, we can look at several buckets of technology to get an understanding of the general capabilities. Also important to note is that while Microsoft has positioned this as a very cloud-friendly OS, almost all of these cloud-related features are also very useful to an enterprise IT environment.
New file system — Included in WS2012 is ReFS, a new file system designed to survive failures that would bring down or corrupt the previous NTFS file system (which is still available). Combined with improvements in cluster management and failover, this is a capability that will play across the entire user spectrum.