Now that the dust has settled and everyone has had a chance to digest the Unified Computing System announcements a bit, I see a couple of salient points--well, I see more, but only have time to blog about a couple of them right now.First and foremost, we have certainly move the bar for everyone. As pointed out in a SeekingAlpha post by Larry Dignan:
Other data center rivals will have to start answering questions about integration between functions, architecture and the potential savings. If anything just the buzz associated with Cisco’s move can dictate the conversation.
In the long run, I think this will drive the industry forward--as Doug pointed out recently, “we are certain over time we will not be alone in this market.” In the near term, however, I see a lot of talking points on why this really isn’t any different or really all that important. Read More »
Yesterday I had a question get asked often enough that we felt it best to answer it on our blog: where should I deploy Unified Computing Systems? We see four main opportunities for unified computing in the near-term:1) Greenfield Data Centers: it is always the easiest insertion of any new technology when the entire facility from the ground-up is being re-thought and we are applying all of the lessons of the past to a new clean-sheet design. The challenge is, of course, that many of the greenfield projects are paused for a while as we take stock of the current economic climate we are all operating in. Still, there are some consolidation projects that are far enough down the implementation path that pausing them is more costly than finishing them- and the Unified Computing System will be there for them. Read More »
Although we just announces the Cisco Unified Computing System yesterday, we already have it in production here at Cisco. We have a number of web, database and legal apps running on it, most of which you cannot access, except for News@Cisco which is open to the public. Listen to Sidney Morgan discuss some of his experiences with the Cisco UCS.
Designing a (successful) product is always tricky; first of all, you need to properly define and wisely select your product requirements. But whatever market segment you are in, your product requirements will change over time. No matter how good you are at predicting market dynamics. Typically, it’s “simpler” to address this variability if your product has relatively short development cycles and if the switching cost for your customers is low. In such conditions, you might lose a cycle but you can get back in your market, with the right product, within few months. Consumer space could fit this description for example. The problem with networking products in particular is that development cycles are instead certainly long: 12, 18, sometimes 24 months from product definition to availability. More importantly, from a customer perspective, the investment involved in networking gears is significant and the product life is expected to span over multiple years to maximize the Return On Investment (ROI). Read More »