Cloud enterprise architecture is the new apps-on-tap, utility computing, central mainframe/thin client orthodoxy (care to recall the time-share computing days … hey, FORTRAN is even still around!).
What’s new is old; except in the case of enterprise cloud, the net-new requirement is optimizing the underlying network infrastructure to deliver reliable, secure, compliant scale and speed for on-demand provisioning of business-critical applications, with minimal human (read: professional consulting) intervention.
At odds with enterprise cloud is the traditional outsourcing services model. Yes, you may end up paying less over time but your deployment, systems integration and app development/provisioning time-to-market is no greater, and in fact, often turns out to be more elongated. What’s more, the delay in deployment and absorption risks loss of competitive and revenue advantage.
I don’t know about you , but I want to be well prepared for the March 30th Cisco announcement
Listening to Cisco SVP Bill Brownell’s invitation, we can definitely expect some very interesting product news, but more importantly a new round of conversations about the right fabric-infrastructure, especially in the context of cloud computing.
That’s why we will have special guests such as John McCool, Soni Jiandani and Tim Gillis in addition of Forrester Research and IDC (see my previous blog)
So as I was willing to be well prepared, I found this interesting blog from Ivan about data center fabric architecture , which obviously grabbed also the attention of some of our smart engineers
Last month, I attended CiscoLive in London, where I delivered a Birds-Of-A-Feather session and had the opportunity to talk to a wide range of customers. One service provider I talked to noted that, in a number of their key customers, the topic of application migration to the cloud was top of mind, and in particular migration of large scale ERP systems and platforms. An interesting topic indeed. And we have a white paper from Cisco Services to help you understand more on the challenges of migrating such enterprise applications to the cloud.
Following my last blog post , I have gotten a number of questions on how we specifically define “fabric” so I thought I’d dig into that a bit more with this post. So, the primarily point is that our definition of fabric it built around a specific set of features and capabilities. It is not tied to specific products or topology. Again, we think it’s important that our customers have choice and not have an arbitrary architecture foisted upon them.
At its most basic level, a fabric is a highly available, high performance shared infrastructure built with integrated, intelligent compute, storage and network nodes that can be rapidly and simply organized around the requirements of a given workload.
We see this fabric as having six specific characteristics:
Open -- based on open standards
Integrated -- breaks down traditional silos with a more holistic approach
Flexible -- allows customers architectural flexibility and choice
Scalability -- easily grows and adapts as the data center evolves
Our Technical Marketing Engineers (TMEs) have delivered a library of technical videos, accompanied with voiceover explanations in clear, simple English, to show you how the Unified Computing System really works. Taken as a whole, this library provides a great functional tour of UCS, but it’s broken down into very digestible, well-defined topics so that you can zero in on topics and features of particular interest.