Grid Computing Explained

An anonymous reader writes "What's different between Grid computing and P2P, CORBA, cluster computing, and DCE? This article provides a cursory analysis of the similarities and differences between Grid computing and such distributed computing systems as P2P, CORBA, cluster computing, and DCE."

Comments

CORBA?

[TheRealMindChild]

CORBA doesn't even FIT into this article, and it is painfully clear when you read it. If this wasn't a free object model, I would say the autor is stretching to sell something, but since that can't be the case, then what is it?

Re:CORBA?

[roboros]

Oddly enough, WSDL and SOAP are mentioned, but never really discussed. And the would be probably better suited than CORBA.

WSDL and SOAP are used in version 3 of the Globus Toolkit, which is a well-known open source grid toolkit. In that version, all grid services are Web Services.

The problem with Grids

[duffbeer703]

The big problem that I see with "Grid Computing" is that 99% of articles about it point out that it is cool and leave it at that. A few articles will point out how GM does rendering for CAD/CAM stuff or how Folding@Home works.

My question is what business problems can be solved with grids? Most people do not work in scientific computing facilities and most engineering departments are overseas anyway.

Re:The problem with Grids

[Uma Thurman]

Grid computing means several things:

-the supply of compute power will equal the demand
-shifts in supply happen automatically
-you pay for what you use

Don't think of cluster computing. That's the wrong idea. Don't think engineering. Those people need clusters, not grids.

Grids are for people who run businesses. Their demand changes all the time, and it's expensive to have to buy computers that can handle the peak load. For example, some types of retailers will do 80% of their business in December. Why should they hang onto the computers all year around?

This is how it will work: you are a business. You call up IBM and you ask for a single processor Celeron machine, with 1 gig of database attached to it. They provide it, maintain it, make sure it's running, and charge you X dollars per month for it.

Then, one day, you discover 100 million dollars in sales that you have to get out the door. You call up IBM and tell them that instead of a dinky Celeron, you need a 32-way machine with a terabyte of database storage. They set you up and you've got the capacity on-line in 15 minutes. A machine like that might run over a million bucks to buy new, but you can use the machine for a lot less than that.

You use that capacity to get the orders out the door, then you discover that your business is back down to the celeron. You call up IBM and have them change you back.

Without grid, you would have to spend a million bucks or more to have that 32 way machine sitting around ready for the two weeks when you needed it. With grid, you only pay for two weeks usage of a million dollar machine, which is a huge savings.

Re:The problem with Grids

[DeepRedux]

On answer to the question of "what are Grids for" is given by the paper The Anatomy of the Grid. I think the paper can be summarized by the following quote from it:

The real and specific problem that underlies the Grid concept is coordinated resource sharing and problem solving in dynamic, multi-institutional virtual organizations. The sharing that we are concerned with is not primarily file exchange but rather direct access to computers, software, data, and other resources, as is required by a range of collaborative problem-solving and resource brokering strategies emerging in industry, science, and engineering. This sharing is, necessarily, highly controlled, with resource providers and consumers defining clearly and carefully just what is shared, who is allowed to share, and the conditions under which sharing occurs. A set of individuals and/or institutions defined by such sharing rules form what we call a virtual organization (VO).