Another Enterprise Connect has come and gone; now that the booths have been rolled away and sales teams begin the process of doing follow up with prospects met at this year’s show, I had some thoughts about UC applications in the cloud.
Unified Communications services deployed from the cloud was all abuzz during the show; from Sprint announcing its Complete Collaboration suite to many vendors discussing how they are moving their contact center offerings to the cloud. Even analyst Zeus Kerravala offered his observations following a cloud panel he moderated during last week’s show.
Specifically, Zeus mentioned that one of the key takeaways he heard during his panel was when organizations are deciding when to implement a UCaaS model, they think about which UC service they currently don’t have and deploy it through the cloud. This had me thinking about what features an organization should look for as they explore the possibilities of a cloud collaboration model.
Mobile video is exploding at a rate unimagined only a few short years ago. Whereas the quick YouTube clip had been a satisfying enough diversion, consumers armed with next-generation devices now demand the latest bandwidth-busting, 2-gigabyte Hollywood opus. The end user wants it on his iPad, and he wants it now.
For the industry at large, this creates no shortage of challenges. According to the Cisco Visual Networking Index, by 2016, 71 percent of global mobile data traffic will be video, placing a heavy burden on the network. But along this next frontier of mobile video there are also unprecedented and exciting opportunities.
Today’s announcement that Citrix is dropping support for OpenStack has reverberated through the clouderati sphere like a new Justin Bieber song through my niece’s third grade class. Super important but will not matter much when the next idol arrives.
In any case, a lot of smart people have written about it. I’ll leave them to explain the whole thing.
But the post that most caught my attention came from Thorsten at Rightscale‘s. We both share something in common: we both build products that connect to cloud API’s. Including vendor who have API’s that claim to be compatible EC2. This experience, I think provides a useful point of view when thinking about API compatibility. Not to mention it creates a jaundiced view of the human soul.
I’ve said it many times and I’ll repeat it again: it’s the semantics of the resources in the cloud that matter, not the syntax of the API. This means that “API compatibility” has to reach very, very deep to be meaningful. Let me give you a couple of examples around EC2.
March 2009 was an exciting time for both for Cisco and for me personally. Cisco launched the revolutionary Unified Computing System, with many observers across the industry doubting if we’d stay the course (and if we’re honest, some truly misplaced derision -- I wonder who is on Planet Zircon now!). And I joined the Cisco Data Center Services team from the Cisco R&D organization! So with the recent third generation launch of Cisco UCS, described very well by my colleague Todd Brannon, I thought it would be a good time to reflect on our data center services portfolio around that time, and where we are now. My previous blogs chronicle part of this journey, however I have to say, the direct comparison I draw here I personally think shows that we have indeed brought a new transformational experience to the data center for our customers. And I’d like to give you my personal recollections on how and what I found out about Cisco’s approach to shaking the incumbents’ lack of innovation in the blade server market.