I don't clearly catch the difference betwenn these two concept. Someone told me that the essential différence is that the cloud computing give you a large space of storage and the grig give more advantages than storage, we can profit to much power with this last.

 

Does any one know more clearly these two concept; and tell us?

Views: 250

Replies to This Discussion

I don't claim to be the expert, but the difference is (I think) in use.

 

Grid represents a scalable framework.  You write your algorithm and your code and use as much computing power as you wallet can afford.  (Useful as some work can be highly parallelizable) .

 

Cloud computing offers storage (true) but it's also represents the applications as well.  Ideally with cloud computing, you don't need to have certain applications on your desktop - as long as you can hit the cloud, you can get, update, and use your data.  

Thanks thomas;

What  I got :

 

Grid - much computing power and can be highly parallelizable

 

Cloud - Storage and dont need to have  certain applications on your desktop ( that's just like server application?)

 

Someone can tell us more?

I think if you look at the history, you will understand some difference.

In my own experience, the grid began with Oracle using it as a type of metadatabase, which would point to multiple databases residing on different but uniform hardware systems.  So if a company had multiple unix boxes and needed to increase the size of their database, instead of purchasing additional hardware they could implement the grid database and combine their multiple unix servers into one database resource.

 

Cloud is much more in terms of it offering not only a database, but also an entire server including the operating system.

The cloud exposes an operating system, whereas a grid exposes a database.

 

But I am no buzz word expert so I might be wrong.

I just talked to a buddy about this, essentially the Oracle Grid product is differant because it runs the DB in memory. So access times are a lot quicker. I don't think it is really a matter of Vs. so much as Grid computing is a way to handle db transactions in a faster way.

 

He said their grid servers had something like 72gbs of ram. Freaking crazy

Please Bradley, wha do you think about Jackie's reaction?

RSS

Happy 10th year, JCertif!

Notes

Welcome to Codetown!

Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.

When you create a profile for yourself you get a personal page automatically. That's where you can be creative and do your own thing. People who want to get to know you will click on your name or picture and…
Continue

Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.

Looking for Jobs or Staff?

Check out the Codetown Jobs group.

 

Enjoy the site? Support Codetown with your donation.



InfoQ Reading List

Anthropic Introduces Agent-Based Code Review for Claude Code

Anthropic has introduced a new Code Review feature for Claude Code, adding an agent-based pull request review system that analyzes code changes using multiple AI reviewers.

By Daniel Dominguez

Presentation: Speed at Scale: Optimizing the Largest CX Platform Out There

Matheus Albuquerque shares strategies for optimizing a massive CX platform, moving from React 15 and Webpack 1 to modern standards. He discusses using AST-based codemods for large-scale migrations, implementing differential serving with module/nomodule, and leveraging Preact to shrink footprints. He explains how to balance cutting-edge performance with strict legacy browser constraints.

By Matheus Albuquerque

Article: Lakehouse Tower of Babel: Handling Identifier Resolution Rules Across Database Engines

Lakehouse architectures enable multiple engines to operate on shared data using open table formats such as Apache Iceberg. However, differences in SQL identifier resolution and catalog naming rules create interoperability failures. This article examines these behaviors and explains why enforcing consistent naming conventions and cross-engine validation is critical.

By Maninder Parmar

AWS Launches Agent Registry in Preview to Govern AI Agent Sprawl Across Enterprises

AWS released Agent Registry in preview as part of Amazon Bedrock AgentCore, providing a centralized catalog for discovering, governing, and reusing AI agents, tools, and MCP servers across organizations. The registry indexes agents regardless of where they run and supports both MCP and A2A protocols natively. Microsoft, Google Cloud, and the ACP Registry offer competing solutions.

By Steef-Jan Wiggers

AWS Introduces S3 Files, Bringing File System Access to S3 Buckets

AWS recently introduced S3 Files, which lets users mount an Amazon S3 bucket and access its data through a standard file system interface. Applications can read and write files using standard file operations, while the system automatically translates them into S3 requests, allowing compute services to work directly with data stored in S3.

By Renato Losio

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service