Cloud - auto-magic or just provisioning platform for your distributed system
Good blog-post from a quite interesting twitter-discussion on cloud technology.
Good blog-post from a quite interesting twitter-discussion on cloud technology.
I'm always shocked by comments like this:
Good blog-post on an old-trick:
Amazon CloudFront delivers your content using a global network of edge locations. Requests for your objects are automatically routed to the nearest edge location, so content is delivered with the best possible performance.
Microsoft, offers a way to host your .Net applications on the Cloud with a pricing model yet to be officially announced, and offers integration with some Microsoft services/applications.
Here are the three criteria I have for determining whether something is a cloud service or not:
That is - how can we expect IT people to be able to strategize and decide on IT direction and tactics if we can't even describe for them what the real issues are in any consistent way. For that, we need a commonly accepted definition, even if it is not great.

Platform components as a service will hit the software marked hard in 2009 and 2010, but until developers and architects understand how to leverage the platform components in a clear and consistent way, they will add more pain than salvation... Read up on some of the architecture axioms and distributed architectures and analyse your current design and architectures before moving to platform component services is advised. :)
The cloud computing market is in a period of excitement, growth and high potential, but will still require several years and many changes in the market before cloud computing -- or service-enabled application platforms (SEAPs) -- is a mainstream IT effort, according to Gartner, Inc.