As with nearly every IT trend, including service-oriented architectures and Web services, just because we're all talking about cloud computing doesn't mean we're talking about the same thing.

I recently joined a LinkedIn/Google group on cloud computing, a member of which posted what should have been an innocent question: Is there a difference between cloud computing and what we know as grid computing? I was ready with my own answer, but overnight about a dozen responses had already flooded in, creating an e-mail chain that offered some interesting nuances on the terminology.

I hope this doesn't get me kicked out of this group, but I thought it might be interesting to reproduce some of these as food for thought. In the interests of privacy I'm not publishing anyone's names, and I've edited some of the definitions for the sake of clarity and length. Here are the top five:

1. "Vendors, as always, blur the real definitions of new terms. In my opinion (and the opinion of others, cloud computing isn't the same as utility computing, which isn't the same as grid computing:

"Grid computing generally refers to resource pooled environments for running compute jobs (like image processing) rather than long running processes (such as a Web site or email server).

"Utility computing generally refers to resource-pooled environments for hosting long running processes, and tends to be focused on meeting service levels with the optimal amount of resources necessary to do so.

"Cloud computing refers (for many) to a variety of services available over the Internet that deliver compute functionality on the service provider's infrastructure (e.g. Google Apps or Amazon EC2 or Salesforce.com). A cloud computing environment may actually be hosted on either a grid or utility computing environment, but that doesn't matter to a service user."

2. "Cloud computing = Grid computing. The workload is sent to the IT infrastructure that consists of dispatching masters and working slave nodes. The masters control resource distributions to the workload (how many slaves run the parallelized workload). This is transparent to the client, who only sees that workload has been dispatched to the cloud/grid and results are returned to it. The slaves may or may not be virtual hosts.

For more enterprise computing news, visit Computerworld. Story copyright Computerworld, Inc.

Whitepapers

• The Trend from UNIX to Linux in SAP(r) Data Centers
• Secure Wireless Printing Options
• Improve Virtual Storage TCO by Comparing Vendors
• Making IT Invisible
• Best Practices for VMware ESX Server
• Virtualizing Storage for VMware Success

View more DATA CENTER whitepapers

Webcasts

• Branch Office Trends and Best Practices
• Data Protection and Application Availability for Your VMware Environment with Veritas NetBackup and Cluster Server for VMware ESX
• Making NetBackup Highly Available with Storage Foundation HA
• Best Practices for Deploying WAN Optimization for Disaster Recovery
• Tips and Techniques for Remote Data Backup and Delivery
• WAN Optimization Landscape

View more DATA CENTER webcasts

Special Reports

• Executive Guide: Storage Heats Up
• Symantec State of the Data Center Report
• Data Centers: At the center of the action
• Executive Guide: Virtualization Reality Check
• Executive Guide: Data Center Decisions
• Get More From Your WAN

View more DATA CENTER special reports