Into the cloud
Cloud computing has been steadily gaining momentum and validity in meeting enterprise needs and this latest global experiment from HP, Yahoo, Intel, University of Illinois at Urbana-Champaign (US), Karlsruhe Institute of Technology (DE) and Infocomm Development Authority (SG) should prove interesting to watch.
The ambitious six-site project is aimed at developing an Internet-based computer infrastructure stable enough to host companies’ most critical data-processing tasks. The project also holds an unusual promise for advances in fields as diverse as climate change modeling and molecular biology.
The project’s large scope will allow researchers to test and develop security, networking, and infrastructure components on a large scale simulating an open Internet environment. But to test this infrastructure, academic researchers will also run real-world, data-intensive projects that, in their own right, could yield advances in fields as varied as data mining, context-sensitive Web search, and communication in virtual-reality environments.
Tim O’Reilly is concerned that though we may move into the cloud for all the right reasons, we will still use the old architectures and lock everyone in as we did with ERPs and other proprietary applications.
…the success of the internet as a non-proprietary platform built largely on commodity open source software could lead to a new kind of proprietary lock-in in the cloud. What good are free and open source licenses, all based on the act of software distribution, when software is no longer distributed but merely performed on the global network stage? How can we preserve freedom to innovate when the competitive advantage of online players comes from massive databases created via user contribution, which literally get better the more people use them, raising seemingly insuperable barriers to new competition?
The “internet operating system” that I’m hoping to see evolve over the next few years will require developers to move away from thinking of their applications as endpoints, and more as re-usable components. For example, why does every application have to try to recreate its own social network? Shouldn’t social networking be a system service?
This isn’t just a “moral” appeal, but strategic advice. The first provider to build a reasonably open, re-usable system service in any particular area is going to get the biggest uptake. Right now, there’s a lot of focus on low level platform subsystems like storage and computation, but I continue to believe that many of the key subsystems in this evolving OS will be data subsystems, like identity, location, payment, product catalogs, music, etc.
How do we ensure openness and interoperability prevail at the end of the day? Seemingly irrelevant for something referring to clouds, but no less important to cloud computing’s success, how too do we ensure the right locations for the physical manefestations of the cloud?
