Thursday, August 28, 2008

Is my blog named wrong?

Somehow I found a link to Wordle, a very cool tool that creates word cloud graphics based on text or URLs. Naturally, I ran through it to see what my grid cloud would look like...

...and promptly found out that my "grid cloud" is actually more of a "cloud cloud."

That last sentence points out several things I've noticed lately:

  • Those of us who have been writing about Grid Computing are increasingly writing about cloud computing, and of course that's no surprise. While clouds are opening up the prospect of distributed computing to a much wider audience than ever, using a cloud effectively means possibly managing many machines effectively. Alternatively, it may mean writing software that effectively runs on many machines simultaneously. In either case, the grid computing industry has been thinking about (and solving!) these problems for years. If you want a firsthand look at the expertise these "grid" folks have in "cloud" efforts, hop onto the Google Cloud Computing group and check out Rich Wellner's contributions. As I said, the grid folks have been thinking about these problems for years (albeit in a slightly different implementation).
  • The term "Cloud" already has far too many meanings in the marketplace (another parallel to grid, come to think of it)
  • If I'm writing more about cloud computing than grid computing, is it time to rename my blog?
I've got a few posts I've been thinking about in terms of the intersection of cloud and grid (and where cloud is going) -- I'll try to get back on the blogging bandwagon and pump some of those out.

In the meantime, I'm not changing the name of the blog. It may be an antiquated name, but at least people know where to find me.

Technorati tags:

Friday, August 01, 2008

I'm all for scalability

I love being quoted by that coffee-roasting, free-diving, Hawai'i living, .NET expert Larry O'Brien, so I was quite please to read my name in his latest SD Times column. He quoted a tweet (yes, I love Twitter) where I quoted a fellow CloudCamp attendee saying "Designing your app to scale is guaranteed failure—it will take too long to write."

Unfortunately (and due primarily to the 140 character Twitter limit), Larry didn't realize that I didn't agree with the guy I was quoting -- I just found it amusing.

I've actually blogged quite a few times about designing scalability into an app. In a 2005 post (Of course scalability matters!), I said this:

Most importantly, [designing scalable software] means acknowledging the possibility, however remote, that you may actually succeed and build something that people eventually use. Many people.

This point applies equally to those designing web sites and those planning on deploying SaaS. If you are going to make it available on the web, and you're not designing for scalability, then you just aren't planning for success: you're planning for failure.
I followed that up with a post a month later, and I was quite pleased to learn that Werner Vogels's viewpoint coincided with my own.

So I wholeheartedly agree with Larry's sentiment:
However, I’m uncomfortable with the idea of dealing with scaling only when it becomes a problem. While laissez-faire attitudes have come to dominate code and design approaches, I still resist the idea of abandoning upfront architectural work.
In fact, when I overheard the comment at CloudCamp, my first reaction was this: the only reason building scalability into your product would hurt you is if your idea is so unoriginal that someone else is 5 minutes behind you.

So: thanks for the mention, Larry. I'm on your side.

(And I really am going to ride over to Sweet Maria's next week, so send me an e-mail)

Technorati tags: