Grid Computing Explained 28
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."
Re:CORBA? (Score:3, Insightful)
Of all distributed computing environments, CORBA probably shares more surface-level similarities with grid computing than the others. This is due to the strategic relationship between grid computing and Web services in the Open Grid Services Architecture.
Oddly enough, WSDL and SOAP are mentioned, but never really discussed. And the would be probably better suited than CORBA.
The problem with Grids (Score:5, Insightful)
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 (Score:2, Insightful)
The distinguishing factor about Grids is that they operate across organizational boundaries. There's no point in doing a single organization Grid. Beowulf clusters? You might have them on the grid as single nodes.
BTW, there is one very well known (in the US) Grid system and there is one production-ready Grid system, and they are not the same.
Re:The problem with Grids (Score:3, Insightful)
-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 (Score:3, Insightful)
Grid requires that you are doing things that don't require too much data to be pushed around (at least not compared to the amount of work that has to be done on the data). For large databases and the like, the problem is just sorting through the data and sending it somewhere else won't help because the effort of sending it there is probably no more than the effort of just looking through it for what you wanted.
Re:The problem with Grids (Score:4, Insightful)
Re:The problem with Grids (Score:2, Insightful)