- 15 Non-Certified IT Skills Growing in Demand
- How 19 Tech Titans Target Healthcare
- Twitter Suffering From Growing Pains (and Facebook Comparisons)
- Agile Comes to Data Integration
Network World - This vendor-written tech primer has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter's approach.
It's difficult to define what the "cloud of tomorrow" will look like because of all the changes happening in the IT industry -- changes to fundamental application architecture, service models and interactions between components. The cloud continues to disrupt IT in new ways so predicting tomorrow is a perpetual moving target.
Understanding that, a clearer picture of the future of the cloud might be gleaned by looking at the current offerings and identifying how they should change to accelerate the cloud market.
[ IN PICTURES: 10 cloud predictions ]
It's important to recognize why the cloud is different and what -- from a technical standpoint -- drives the disruption it causes:
These differences are forcing enterprises to change their cloud use habits and are limiting functionality and what can be done within the cloud. The applications and services that have already made the jump to cloud have most often been Web-based applications specifically designed to work in the cloud.
Of course, there are many applications that have not made transition -- these are mostly enterprise applications such as CRM, ERP, B2D, SCM (and just about any other three letters you choose to combine). These applications are "the hard stuff" that makes a business run.
These applications are deemed difficult because they are restricted by the limitations imposed by cloud architecture. This leaves two choices -- change the applications or change the cloud. As in the technology industry, all things evolve and these applications will eventually be "re-written" or discarded as newer ones are developed. However, there is an opportunity to change the clouds so that they do more allowing us not to wait for the evolution of applications.