So that you don’t think we’re talking about hype
I took a look at the previous post and I realized that it can also be read in the hype/firemen-ish code. Behold Grid Computing!
Look at this paragraph from (the famous, but too little read) What is Web 2.0 by Tim O’Reilly:
Operations must become a core competency. Google’s or Yahoo!’s expertise in product development must be matched by an expertise in daily operations. So fundamental is the shift from software as artifact to software as service that the software will cease to perform unless it is maintained on a daily basis. Google must continuously crawl the web and update its indices, continuously filter out link spam and other attempts to influence its results, continuously and dynamically respond to hundreds of millions of asynchronous user queries, simultaneously matching them with context-appropriate advertisements. It’s no accident that Google’s system administration, networking, and load balancing techniques are perhaps even more closely guarded secrets than their search algorithms. Google’s success at automating these processes is a key part of their cost advantage over competitors.
It’s also no accident that scripting languages such as Perl, Python, PHP, and now Ruby, play such a large role at web 2.0 companies. Perl was famously described by Hassan Schroeder, Sun’s first webmaster, as “the duct tape of the internet.” Dynamic languages (often called scripting languages and looked down on by the software engineers of the era of software artifacts) are the tool of choice for system and network administrators, as well as application developers building dynamic systems that require constant change.
If we admit that the phase of software as an artifact has passed away and its place has been taken by the software as a service, is obviously that on the hardware side more-more flexibility is needed. Practically, this grid computing thing does exactly this: includes the hardware into the application.

