The long-rumored changing of the guard at VMware finally took place last week and with it came down a stubborn strategic stance that was a big client dis-satisfier. Out went the ex-Microsoft visionary who dreamed of delivering a new "cloud OS" that would replace Windows Server as the corporate standard and in came a pragmatic refocusing on infrastructure transformation that acknowledges the heterogeneous reality of today's data center.
Paul Maritz will move into a technology strategy role at EMC where he can focus on how the greater EMC company can raise its relevance with developers. Clearly, EMC needs developer influence and application-level expertise, and from a stronger, full-portfolio perspective. Here, his experience can be more greatly applied -- and we expect Paul to shine in this role. However, I wouldn't look to see him re-emerge as CEO of a new spin out of these assets. At heart, Paul is more a natural technologist and it's not clear all these assets would move out as one anyway.
B2B communication, with its original form of EDI messages, is the oldest and unfortunately the least flexible form of integration between systems and different enterprises. Many enterprises run B2B gateways on-premises or have managed service contracts for “their instance of their B2B Hub.”
I’ve received over the past months an increasing number of inquiries from Forrester clients asking for the future of this approach and the market trend. This is what I usually explain:
Your future cloud/legacy integration should cover your business partner and your SaaS applications. Cloud computing is disrupting the integration space! Why? Traditionally, you had two very distinguished integration scenarios. Either, it was about the integration between multiple systems within your enterprise — middleware software, with product categories like EAI, ESB, CIS, and BPM, was the matching solution, as all systems have been on premises in the past. Or, it was about the integration with your business partners — the well-established B2B/EDI gateways and managed services were the matching solution over the Internet (or VANs). However, cloud computing disrupted the space already: Suddenly parts of your business unit’s applications are in the cloud on packaged SaaS applications, and they needed to be integrated with your on-premises legacy. Or, you and your business partners even use the same SaaS applications, and B2B traffic is as simple as moving data from one tenant to the other tenant on the same cloud platform. To face this trend of an increasing variety of integration, a good cloud integration strategy should look at synergies between the cloud/legacy integration scenarios with your business partners and the SaaS tenants of your own enterprise holistically!