Some may be interested to read Perl Catalyst and Cloud Computing, which introduces the concept of cloud computing, discusses why this is important for Perl, what Perl resources are currently available and details some plans regards the future cloud computing and Perl ('think "DBI for cloud computing"').


Replies are listed 'Best First'.
Re: Perl Catalyst and Cloud Computing
by grinder (Bishop) on Jul 17, 2008 at 14:58 UTC

    Slightly off-topic, but ...

    From TFA, "Currently, there are only two Perl projects relating specifically to cloud computing of which I am aware. There's Jeff Kim's great work on Net::Amazon::EC2 [...] and then there's the Net::Cloud (link forthcoming) project. I registered that namespace about two years ago..."

    So in fact there's only one project. The other is vaporware and the CPAN namespace has been squatted for two years. Not that I'm bitter, but long-term namespace squatting is a real pain. Three times over the past few years I've found what at first glance would be the solution to a particular problem. On closer look it's just a movie set, where you open a door and there's just plaster and wood struts, and blue sky on the other side.

    I wish people would get over this aspect. So what if someone else releases Net::Cloud before you? Firstly, the likelyhood is very low. Secondly, there's a fair chance that you'll probably wind up collaborating on the project if it the name is sufficiently well calibrated to the problem domain. Thirdly, when/if both of those avenues don't pan out, you could always pun(t?) the issue and name your module Net::Altostratus.


    • another intruder with the mooring in the heart of the Perl

      Not in defense of namespace squatting or anything, but Net::Cloud is definitely an active project and if you are interested please join us on channel #net-cloud I know frank is hot to release code, I think he told me he's rewriten it several times but is finally feeling like it's in usable shape. As for the time lag, the explanation given to me by frank is that EC2 stayed in closed beta much longer than he originally expected so releasing code would have had very limited application. Then he got very busy with other projects. But we all agree vaporware is bad. Thanks, Jnapiorkowski