Java and .NET APIs are pretty darned good at integrating with the cloud based platforms for which they were designed, but when it comes to the interoperability of the two, or the migration of older applications to the cloud, simple tasks can be problematic. Accessing the file system in one of your legacy applications, or even writing something to the registry? You’re going to run into problems when you move those applications to the cloud. At JavaOne this year, JNBridge is proposing a solution.


“We believe that what is typically discussed under the rubric of cloud interoperability is so insufficient it will destroy the promise of the cloud,” said Wayne Citrin, CTO of JNBridge. “JNBridge’s position is that ‘Cloud Interoperability’ must encompass full Cloud-to-Cloud access, where any cloud service can access any other cloud’s service, full Cloud-to-Ground access, where any cloud service can be consumed from any client or on-premise platform, and full interoperability within a cloud service. In order for this to work, developers need the ability to write cloud services using any platform, easily, simply and quickly, and regardless of the cloud vendor. Our vision of cloud interoperability is any object, on any platform, in any language, anywhere, and at any time.”


If you’re at JavaOne, and you’re interested in learning more about JNBridge, they’re holding an “unconference” session at JavaOne titled “Interoperability issues in the cloud... and how to solve them” on Tuesday, September 21 at 1 p.m. Pacific.

Why Interoperability Must Succeed for the Cloud to Survive

JNBridge