Ideas….

Last week Geva Perry wrote a post published on GigaOm called Who Will Build the LAMP Cloud.  In it he speculated on current cloud providers that may be interested in building a PaaS (platform as a service) offering of the traditional LAMP stack.  A few days later James Urquhart responded with his blog post entitled Does Cloud Computing Need LAMP.  In it he questions whether the Linux and Apache piece are really necessary in a PaaS offering.  He then goes on to question the usefulness of P languages (PHP, Perl, Python) and MySQL, using a comment to Geva’s post as a jumping off point.  Geva then comments back with a post on his own blog entitled Who Will Build the LAMP Cloud? And Who Cares? In it he agrees with James’ comments on not caring about the LA in LAMP, but says:

James’ last question: “Is the ‘open sourceness’ of a programming stack even that important anymore?” is a good one, but orthogonal to the discussion about a LAMP/PHP cloud, in my mind.

So why has this conversation gotten me in a tizzy and forced me to write two blog posts in one week?  Well two reasons:

1. Many web based open source projects are built on the back of P languages (PHP, Perl, and Python)
2. The cloud exists to make technology easier for the masses.

Now before I go any further I will disclose that the first language I learned was PHP.  The second one was Perl.  While I know there are wars that start on listservs about what languages are better, that is not the purpose of this post, so put it out of your head and don’t say anything about how much you think PHP sucks in the comments.

Web based open source projects are built on the back of P languages

Now I could write something about this, but I like lists.  So here is a brief off the cuff list of what open source projects use P languages:

1. MediaWiki (PHP)
2. WordPress (PHP)
3. Bugzilla (Perl)
4. Drupal (PHP)
5. Plone (Python)
6. Moodle (PHP)
7. AWStats (Perl)
8. MovableType (PHP and Perl)
9. Subversion (Python and C)
10. Trac (Python)

Now, I’m not going to argue the merits of how good each of these piece of software are. Again that’s not my point.  But they are popular whether you like it or not.  And to just dismiss them would be foolish.

The cloud exists to make technology easier for the masses

Google Docs makes it easier to get to files you need to edit.  Heroku makes it easier to deploy Ruby on Rails apps.  Amazon EC2 makes it easier for you to deploy a server.  The fall out of the cloud is that technology suddenly becomes much easier to create and deploy.

So what happens when my mom wants to write her own blog.  Well, most likely she heads over to WordPress.com and creates a blog for herself.  And if she needs a little more, then she signs up for the WordPress Premium services.  But what if I want my own blog.  Well right now I have my friend hosting my stuff.  But what if I want it hosted elsewhere and I don’t want to maintain servers (since I do that all day long).  My only option right now is to do what my mom is doing, but the reality is, that’s not what I want.  I want something like Heroku but for PHP.  And if I had it, I could install any of the PHP applications listed above.

And I think this conversation is very pertinent given that Google just announced its open source learning management system written in Python and intended to be deployed in Google App Engine.  This could potentially be a big blow to Moodle who doesn’t have a cloud to turn to.

Conclusion

So yes a PHP based cloud does matter.  And yes it should be built because there are lots of people clamoring to use it (or who have already figured out a way).

And yes this blog post could be more coherent.

I’ve been a bit crazy recently with attending conferences and presenting, so I’ve been a bit quiet. And I might continue to be given my current workload. But I’ve come here to write for self serving purposes. After all, what good is a blog if you can’t use it for self serving purposes (the answer is no good).

I was asked to write a piece on the cloud (I know you’re shocked) in the upcoming issue of Educause Quarterly which will be dedicated to the cloud. If you’re peer reviewing for that particular journal, we will now pause so that you can close the window (the peer review process is double blind) ………………………………………………………………………………………..

Ok good. Now that they’re gone. Here is a link to a first pass at my article:

Defining Cloud Computing

Essentially its a rehash of my presentation at NERCOMP with a bit more depth and significantly fewer audience members asking questions (not that I mind questions…that was my favorite part by far. its just that i didn’t actually get to finish the presentation properly because there were so many questions). The article itself defines the cloud, and then uses videos to illustrate each of the definition’s points.

Questions, comments, and feedback are welcome.

And yes, I was trying to be funny when I used the cloud to deliver an article on the cloud (see web address of article for more details).

A number of places asked me to provide my initial first impressions of the survey I did on Cloud Computing in Higher Education.

My first impression is that survey respondents don’t understand what the cloud is, but that shouldn’t have been a shock to me, most people don’t know what it is.  Admittedly this lack of understanding could be due to the way the survey was structured; but even after a couple of tweaks to the order of sections (I moved Software to the front of the survey and Platforms and Infrastructure to the end), respondents were still having a hard time understanding what was what.  I’ll most likely need to do some clean up on the survey, but I think for now I have a great understanding of what is going on in Higher Education in terms of the cloud.

In the survey I tried to define the three main components of the cloud: Software-as-a-Service, Platform-as-a-Service, and Infrastructure-as-a-Service.  After the survey was completed, I realized that I’ll need to do a better job of defining things for the audience members in my NERCOMP presentation.  Something that I though I could spend 10 minutes on will probably need a solid 20 minutes so that everyone can be on the same page.  I think diagrams and other visual aids might really help people understand what these different components are, and how they correspond to computing they are already using.

My second impression is that institutions are very comfortable with using Software-as-a-Service.  Below is a graph showing SaaS usage among respondents.  Facebook is of course the leader in the SaaS cloud race, with Twitter and Google Docs coming in right behind them.  What I think is the most interesting though is that overall, Google has the highest share of the marketplace.

As far as PaaS and IaaS, most institutions are not using these services.  I’m hesitant to show results from these sections of the survey since so many respondents confused software for platforms or infrastructure.  Once I clean things up, I’ll provide more information.  Suffice to say though, few if any institutions are using Infrastructures or Platforms in the cloud.  Those that are are using Amazon Web Services (for infrastructure) and Google Code (for platform).

More to come later.  And thank you to everyone that took the time to take my survey.  It has been eye opening and hopefully will make me a more informed speaker.