Sadly, I'm not in San Diego this week to hear Tony Bates' keynote coming out speech in person. (Well, happily, actually, as I'm skiing with family in Vermont -- great snow today!)
But I do have context on this announcement as I've been analyzing both the consumerization brand, Skype, and the enterprise brand, Lync, for years now. When Microsoft did the Skype deal going on two years ago, I posted on Microsoft's opportunity to bring Skype values to Lync customers and deployments as it has acquired a consumerization brand, a cloud service to sell, and a chance to do B2B communications properly.
At a glance from afar, it looks as if almost two years later, Microsoft under Microsoft Skype president, Bates, has kept its eye on this prize. What I see from Vermont is that Microsoft is in fact:
Re-humanizing business communications, a good and much-needed thing. (Okay, I like the phrase re-humanizing. It must stem from having played rock n' roll fulltime in the Police-laden "rehumanize yourself"'80s.) If people can't easily use the tools, then they won't bother. This is the essense of consumerization: people using readily available and affordable technology on their own to get work done. Microsoft appears to be understanding and focusing on the consumerization values of Skype. We'll wait to see the Lync-meets-Skype experience, but it sounds good on paper, anyway.
Thanks to the good work of my colleagues Eve Maler and Jeffrey Hammond, we have a new Forrester Wave on API Management Platforms, including evaluations of Layer 7, Mashery, WSO2, Intel, IBM, Vordel, and 3Scale. I won't spill the beans on the leaders, but I will share some of their analysis with my own interpretation to explain why you must care. First, let's define API management platforms as:
Middleware that developers use to publish and configure interfaces and that applications use at runtime to connect to the data services they need.
Here's why API management platforms matter:
As you build mobile apps for customers, partners, and employees, you need apps that perform well over the last wireless mile. And that means you need a great, RESTful API that provides design-time and runtime access to data services hosted by your on-premises applications. Think of it as "cloud-connect" technology that lets the data inside your datacenter get out and back (securely) to the mobile app that needs it. As mobile apps get more and more transactional, the need for API management platforms will become even more critical.
You are just getting going on the number, breadth, and complexity of the data service APIs you will need to build and operate. As mobile apps get interesting, with transactions, integrated applications, and more and better content and collaboration, you will need solutions that handle all those integration points. Think of it this way: RESTful interfaces give you the means, but now you need a system to handle the sheer number of APIs you are and will be building.