Henry Lee III

Private and Public

I’d like to suggest we add a definition of private versus public clouds to this page. The industry is embracing these terms and even starting to talk about “hybrid clouds” that are a combination of both public and private.

Private Clouds can be defined as: Private clouds use the public cloud architectures and methodologies but are deployed by a single organization inside the firewall. Resources are typically not shared with outside parties and full control is retained by the creating organization.

An example of a private storage cloud is: Private Cloud storage is typically a loosely coupled architecture, where the nodes don’t need to talk to each other to facilitate writing in parallel to a single file spread across multiple nodes. Instead meta-data operations are centralized enabling the data nodes to focus on delivering data to applications or users. Examples include ParaScale, Hadoop and mogilefs.

Changes Made

Moved the text from the Introduction into a heading called "Brief". AdityaTandon (talk) 07:57, 8 October 2008 (UTC) Aditya Tandon

Apple

I think Apple, Inc. should be added to the list of companies heading the "cloud movement". Since it has released it's new "MobileMe" service, it now has users doing a lot of cloud computing. —Preceding unsigned comment added by Robo56 (talk • contribs) 14:54, 13 September 2008 (UTC)

• I'm unconvinced; the point is to illustrate what cloud computing is and Apple is well known to be a hardware company... your average joe thinks of ipods, iphones and macs. Conversely when one thinks Google you thinks Internet/cloud. That's not to say Apple doesn't get credit elsewhere for their efforts, just that they're not the best example. samj (talk) 08:09, 17 September 2008 (UTC)

Cloud Storage

Added some information on it, with some comparison between the traditional way and how it is now. Bruce404 (talk) 19:36, 1 July 2008 (UTC)

• Good idea... need some good refs for this. samj (talk) 08:10, 17 September 2008 (UTC)

Cons

The article made no mention of the downside of cloud computing particularly the privacy issues with this technology. 78.86.217.191 (talk) 09:56, 19 September 2008 (UTC)

This article has a "Potential advantages" page. Wouldn't it make sense to add a "Possible Disadvantages" page for the sake of continuity? Wikipedia tries to be as non-objectionable as possible, so it seems like a good idea. --Jnorm (talk) 13:58, 27 June 2008 (UTC)

Its a good point i think disadvantages also should be added. Kalivd (talk) 06:23, 26 July 2008 (UTC)

its a great idea.disadvantages should added so as to make people understand abt the article very well.Anoopnair2050 (talk) 15:11, 28 July 2008 (UTC)

Cons about cloud computing any argument against adding the same to the article page

1. It’s not secure.
2. It can’t be logged. Tied closely to fears of security are fears that putting certain data in the cloud makes it hard to log for compliance purposes.
3. It’s not platform agnostic. Most clouds force participants to rely on a single platform or host only one type of product.
4. If you need to support multiple platforms, as most enterprises do, then you’re looking at multiple clouds. That can be a nightmare to manage.
5. Reliability is still an issue.
6. Portability isn’t seamless. As all-encompassing as it may seem, the so-called “cloud” is in fact made of up several clouds, and getting your data from one to another isn’t as easy as IT managers would like.
7. This ties to platform issues, which can leave data in a format that few or no other cloud accepts, and also reflects the bandwidth costs associated with moving data from one cloud to another.
8. It’s not environmentally sustainable.
9. Cloud computing still has to exist on physical servers. As nebulous as cloud computing seems, the data still resides on servers around the world, and the physical location of those servers is important under many nation’s laws.
10. The need for speed still reigns at some firms. Putting data in the cloud means accepting the latency inherent in transmitting data across the country and the wait as corporate users ping the cloud and wait for a response.

Kalivd (talk) 07:17, 1 August 2008 (UTC)

'Advantages' and 'Disadvantages' sections tend to read like datasheets and some 'advantages' are also 'disadvantages' (eg security can go both ways). I hope you are all satisfied with the 'key characteristics' section which should be unbiased statements of fact.

Regarding your specific points:

1. FUD. cloud computing is often more secure (particularly in terms of availability and integrity) than legacy systems.
2. FUD. there is no reason cloud offerings cant be logged, and most are. getting access to the logs can be difficult though so your comment is partially accurate.
3. if you have ever tried to deploy linux software in a microsoft shop or vice versa you will in fact appreciate the flexibility that not having to buy infrastructure affords you
4. again, there's nothing stopping you from using multiple products/platforms/providers (in fact it's easier as you don't need to invest)
5. Reliability is usually better than legacy systems
6. Portability is typically addressed via APIs which are settling down - yes this is a valid concern but no moreso than proprietary file formats
7. See above
8. FUD. You really think it's better to have every man and his dog running servers? I guess you would also argue that we should shut down the power stations and run diesel gensets too? Cloud is Green.
9. Cloud computing need not necessarily exist on physical servers, but the jurisdiction problem is real. Providers like Amazon are making 'local' datacenters available for europeans (others will follow), but harmonisation of regulations will become increasingly important going forward and is just a side effect of globalisation.
10. Bandwidth and latency requirements are highly application dependent; fast pipes are prevalent nowdays and solutions like gears help where they are not available. In any case moving infrastructure outside almost always helps distributed enterprises (as most are these days, with road warriors, work from home, decentralisation, etc.)

I agree that there are outstanding issues that need to be addressed, but I also believe that they will in due course. Conversation (like this) is the first step. samj (talk) 09:38, 1 August 2008 (UTC)

Alright, can you collectively list out the disadvantages of cloud computing so that i can get a clear picture of the cons against the usage of cloud computing. Kalivd (talk) 06:00, 2 August 2008 (UTC)

As I said before: Advantages' and 'Disadvantages' sections tend to read like datasheets and some 'advantages' are also 'disadvantages' (eg security can go both ways).. A great example is Gartner claiming that the very opaqueness that makes cloud computing attractive to many (that is, that you don't need to see or care about what goes on inside) is in fact one of its greatest dangers. Anyway I'll run through and make sure the points are balanced.

I would appreciate the improvement.. Thank you. Kalivd (talk) 07:10, 2 August 2008 (UTC)

HTML? JavaScript? Ajax?

These have very little to do with cloud computing. I am removing them until someone gives me a reason they are there. — ^FatalError 07:52, 1 August 2008 (UTC)

Thanks for the feedback. Ajax enables processing to be done on the client side. Existing cloud based software (eg Salesforce, Facebook, Google Apps) uses Ajax extensively and indeed could not exist without it, so I would argue that it is a critical component of cloud computing. OTOH I agree with you that HTML and Javascript by themselves aren't interesting in the context of could computing, in the same way that TCP/IP is not really relevant. Let's leave Ajax and drop the others. samj (talk) 08:34, 1 August 2008 (UTC)

Adobe AIR? Silverlight?

Any comments on the suitability of Adobe AIR and Silverlight? I've thus far left them out because they aren't true standards (although some components of AIR have been released?)? samj (talk) 08:34, 1 August 2008 (UTC)

Anyone? samj (talk) 06:37, 2 August 2008 (UTC)

Ok I've done some more research myself:

• Microsoft Silverlight sounds very proprietary and this doesn't seem likely to change any time soon.
• Adobe AIR is a similar story, even if the Adobe Flex component is partly open - the SDK's MPL'd but the tools to view (Flash) and create the content will remain proprietary.

Accordingly I don't see any point in listing either amongst a swarm of other open standards but am still interested to hear about how others feel on this point. samj (talk) 07:19, 2 August 2008 (UTC)

Cloud Computing page suggested/request edits

Sam

The Cloud Computing page should be updated to include a few items. You appear to be active in this section and I cannot edit it due to a business relationship with one of the companies involved. Particularly, this sentence:

The cloud computing "revolution" is being driven by companies like Google, Red Hat[9], Salesforce and Yahoo! as well as traditional vendors including Hewlett Packard, IBM and Microsoft[10] and adopted by individuals through large enterprises including General Electric, L'Oréal and Valeo[11][12].

This sentence lists Google, Red Hat, Salesforce and Yahoo as leaders/drivers in cloud computing. It should begin with Amazon, http://en.wikipedia.org/wiki/Amazon and 3tera http://en.wikipedia.org/wiki/3tera, who are pioneers in the efforts to offer commercial cloud services.

Among the large enterprises, you should also include British Telecom, http://en.wikipedia.org/wiki/British_telecom, who is running on of the largest 3tera clouds in the world.

Additional, I suggest expanding this sentence into one or several paragraphs: Commercial offerings need to meet the quality of service requirements of customers and typically offer service level agreements[6]. Open standards and open source software are also critical to the growth of cloud computing[7].

This sentence is very accurate and important. Many of the commercial offerings fail to offer service level agreements or open standards, let alone suppor open source software (Google, Amazon and Yahoo, as far as I understand, do not but I am not an expert in this area:

Jonahstein 17:10, 5 August 2008 (UTC)

Cloud vs Grid

Cloud computing is often confused with grid computing. Grid is a larger concept that allows access to many kinds of resources, including clouds. As such, a cloud is a resource on the grid. This confusion comes from the improper use of grid as a synonym for cluster and from the expansion of the term cloud (which originated as a term for compute access) to include storage (thus making it closer to a synonym to than to its utility computing origins). The majority of cloud computing infrastructure currently consists of reliable services delivered through next-generation data centers that are built on compute and storage virtualization technologies. The services are accessible anywhere in the world, with The Cloud appearing as a single point of access for all the computing needs of consumers. Commercial offerings need to meet the quality of service requirements of customers and typically offer service level agreements[4]. Open standards and open source software are also critical to the growth of cloud computing[5].

Reverted unreferenced, uncommented, controversial edits by numbered user. samj (talk) 08:44, 9 August 2008 (UTC)

More edits have been reverted and I had an offline discussion with the editor (Rw2) which included:

Anyway discussion is good but changing large swathes of an article with contentious views based on opinion pieces, blogs and an ancient reports without first obtaining consensus via the talk page is not on. Usually ancient isn't such a bad thing but the report you cited predates cloud computing by half a dozen years and fails to account for subsequent shifts in the grid area.

Furthermore it takes an otherwise quite clear definition of 'a "super and virtual computer" is composed of a cluster of networked, loosely-coupled computers, acting in concert to perform very large tasks' and replaces it with meaningless drivel that could apply to many different types of computing: 'creating a hardware and software infrastructure that provides dependable, consistent, pervasive, and inexpensive access to high-end computational capabilities'. You could toss this on cloud, mainframes, distributed computing, centralized computing and no doubt hundreds of other computing articles and it would be impossible to differentiate between them.

Anyway, grid and cloud are accepted to be different things; if that weren't the case a new moniker would not have been invented. Yes there are similarities if you drill down to virtual machine providers like GoGrid, Amazon and Sun Grid (it's no wonder then that some of these providers have 'grid' in their name), but the similarities end there. Like it or not, in the eyes of the public grid is about high performance computing, batch jobs and coordination between large clusters run by different administrative domains. Most of the articles talking about cloud these days are actually talking about saas providers like google apps for example.

The point is that wikipedia readers should derive clarity rather than confusion from our articles, and it's our job to impart the consensus view on a subject while citing relevant, verifiable, notable references rather than anything we can find which reflects our views.

samj (talk) 06:05, 26 August 2008 (UTC)

Centralized Computing

I think we should discuss centralized computing... cloud computing is simply a buzzword for a flavor of centralized computing. Basically it's a fancy "futuristic" name that these upstart companies use because it is much easier to market. Technically, the differences are pretty insubstantial. The only difference I can think of is that the network is bigger. Software is stored on a central server, and computers access it via a network. --72.39.35.178 (talk) 16:50, 13 August 2008 (UTC)

• Strongly Disagree for reasons that should be obvious, not the least of which is 15,600,000 hits for 'cloud computing', 62,000 for 'centralized computing'. USPTO also just declared cloud computing both descriptive and generic which would suggest that the term (which appears in at least one dictionary already) is here to stay. Furthermore, there are both distributed and centralized aspects to cloud computing, particularly when you start talking about peer-to-peer applications (which have no place at all in centralized computing). I'm surprised we're having this discussion at all but nonetheless since you've suggested (twice now) that cloud computing be merged into centralized computing it belongs on the latter's talk page. samj (talk) 08:19, 15 August 2008 (UTC)

Sam Johnston, you are not the only person I want to read my comment. Don't go and "archive" it just because *you* don't like my comment or want to discuss it. --72.39.35.178 (talk) 06:01, 7 September 2008 (UTC)

I disagree too. There is an implicit message in "Cloud Computing" that the data and computation is "someone else's problem". A workgroup email server on a remote site is not on the cloud. Furthermore, cloud application architecture is all about having many, many more servers than "a central server". There is one more datacentres, each with a number (possibly a few thousand) servers, with disks and interconnected by high speed networking. The disks fail, the servers crash, yet the cloud keeps working. All the old application designs that worked well on single server, even small cluster systems no longer apply. SteveLoughran (talk) 21:06, 7 September 2008 (UTC)

I am not talking about email. I am talking about things like Citrix XenApp. How is "cloud computing" any different other than simply having a backup server? --72.39.35.178 (talk) 18:33, 8 September 2008 (UTC)

Citrix looks like it is doing something that makes the clients look like thin terminals on a remote machine. But you know what? That's only one design, and its not how everyone else works. Look at Hadoop and read the MapReduce paper to see what other people are doing in their datacentres. This isn't the stuff old mainframes did; by embracing farms of commodity (and unreliable) computers, those people who are building the datacentres have suddenly taken a leap in what they can do. If you look at my slides [[1]] you can see that the jump from a cluster to a datacentre with a farm of computers and a high speed network fabric changes a lot of the assumptions. XenApp is an attempt to host existing apps on such an infrastructure. That doesn't mean its the right thing to do, just a stop-gap measure while the new architecture evolves and people outside google, Microsoft and yahoo start coding for it. SteveLoughran (talk) 21:26, 8 September 2008 (UTC)

Could you give me something more substantial than agriculture analogies and motivational speeches about evolving assumptions and leaps and whether or not "it's the right thing to do?" Networks are not made of cloth and I do not grow corn in my computer. Keep your paradigms in your pants and just explain how it is all hooked up--I'm way more confused by jargon than a highly-complex but straightforward technical explanation. --72.39.35.178 (talk) 18:36, 9 September 2008 (UTC)

Cloud computing stubs

In the absence of a cloud computing stub and for want of somewhere better, please list cloud computing stubs/requests here for now (in alphabetical order):

• GoGrid
• Heroku
• Mosso (web host)

Introduction paragraph

The introduction para is very very long, It just looks like a sea of blue links rather than a definition to me. As i go on reading, the very first para itself confuses me to such an extent that i really care a less about reading the whole article, thought of adding a suitable template for the cleanup purpose but before doing the same would like to discuss about this on the talk page. Any comments appreciated. Kalivd (talk) 14:39, 8 September 2008 (UTC)

someone just added to it earlier today, and yes, it does need taking a sharp knife to it by someone. Go for it! —Preceding unsigned comment added by SteveLoughran (talk • contribs) 16:24, 8 September 2008 (UTC)

I just did a few changes Sanjiv swarup (talk) 02:41, 9 September 2008 (UTC)

I feel Except for the first para rest all be put in a seperate para which speaks more about cloud computing. As on of the Wikipedian has mentioned above about the confusion it creates at the first instant. So putting it in proper paras might just help.

Dhoomady (talk) 07:18, 11 September 2008 (UTC)

It appears that the length issue has been addressed, so I removed the tag. momoricks ^talk 03:13, 10 October 2008 (UTC)

requested expansion

Are there any legal issues related to the security of cloud computing? For example, what are the legal implications of the use of cloud computing to process sensitive information? 69.140.152.55 (talk) 19:10, 10 September 2008 (UTC)

• Yes, of course there are - that discussion is just starting to heat up now and it would probably be worth documenting here as consensus is reached. Thanks for the suggestion. samj (talk) 07:13, 12 September 2008 (UTC)

definition

Is ad-hoc network cloud computing? Is brainstorming a model of cloud computing? --Ramu50 (talk) 02:54, 12 September 2008 (UTC)

Any definition that starts with 'means' and goes on as this article begins is a really poor definition. The definition includes the word 'cloud' several times - in itself a poor move - which itself is never further defined. —Preceding unsigned comment added by 81.50.46.9 (talk) 11:13, 15 September 2008 (UTC)

• Thanks for the feedback. Fixed (hopefully). -- samj _in^out 23:16, 20 September 2008 (UTC)

＠＠ what do you mean by the word 'mean'. Though I think this video does a quite clearn and structure. Somehow for the past few days, I think cloud computing is just simplifying the structure of database into object-based orientation (I am not talking about ORM or OODBMS) which is a faster way of accessing data. Traditional RDBMS and ORMs seems like it is more suitable for HPC, Supercomputer and other high performance application, thus not suitable for desktop. The object-based I am talking about is the UML model. I think mobile device is doing so well, because the engine that runs the OS is built by a framework, which is drastically different from desktop kernel which is so complex, that is why things like Driver will take so long to write. However, when the engine is built by a framework, everything is so structured by concepts like CRUD, ACID...etc that implanation are offloaded thus you retrieve thing so easily. Model that use it are ActiveX, ADO, OLE, Silverlight, Flash, C#...for more info see the stuff I write before [Template talk:Databases Click Here]. --Ramu50 (talk) 03:31, 28 September 2008 (UTC)

Can anybody name me a normal desktop computer software which uses internet and could not be considered "cloud computing". And of course explanation why? --82.203.173.213 (talk) 09:44, 12 October 2008 (UTC)

Google Chrome

Can this article please be more neutral? Google is not the center of the universe. Citing Chrome, for example, was a bit too much for me. More traditional browsers, such as IE and FF deserve the merit much more than that piece of failure called Chrome. —Preceding unsigned comment added by 24.16.37.118 (talk) 08:20, 20 September 2008 (UTC)

• I'm on OS X so I don't use Chrome (yet), but we need more from our browsers in terms of performance, scalability and security (I've lost count of the number of times I've lost a bunch of tabs to Firefox crashing and I haven't had a Windows box to use IE on since... what... 2005). IE8 might be a contendor, and possibly FF3, but the point was that cloud computing demands a new breed of browser. -- samj _in^out 23:16, 20 September 2008 (UTC)

Easy to understand Cloud Computing

Cloud Computing is a type of New World Wide Web Infrastructure you might want to call it, whether or not the infrastructure will pertain to only mobile devices, desktop or even hybrid is not really clear.

Traditional World Wide Web work like the following

• Database (Server)
• Purpose-based Server (server that perform Services / Application, Browsing (Web), Gaming, Multimedia Broadcasting...etc.)

via

• Internet Cloud (2 parts: Infrastruture)

Hardware Infrastructure (DNS, Service Provider (ISP)...etc.) and Algorithm

Abstraction Infrastructure - They are thousand of Cloud in the entire internet, where each cloud represent a field of study (when you try to find stuff, such as on Google, Amazon, Yahoo, or any type of search engine) the Engine will use an Algorithm (or a Logical flow chart that try to find the most appropriate information for your accordingly).

The Semantic Web has developed by MIT define a clear set of method using programming language for categorizing each field of studies which are stored as prototype or netrual data.

• Your Computer

Cloud Computing

• Database (traditional Database, e.g. Data Center)

Purpose-based Server (virtualize)

• Internet Cloud

Service Provider (there is a catch, see Below)

• Your Computer (application are virtualize)

Note that Cloud Computing only accelerate the speed of processing, because application, services...etc. So the definition of Cloud Computing means that you can be anywhere in the world however, the Hardware Infrastructure of the internet cloud doesn't require any DNS, NetBIOS, LMHOST file so basically you are kind of connecting P2P. However, 90% of the people on the market right now is getting one information extremely incorrectly. That is Virtualization is a very object-orientated based meaning that the objects are more like container and the container can only obtain a certain type (or range) of data and they usually require API to communicate each other while API are written by IDL (Interface Definition Language) and several other Schema (definition language or languages that teaches computer how the language works), they are not flexible to semantic constraints and are doesn't have the capability to many variations.

In order for application to perform really well they need to be written in a topological structure where each stages and levels of coherency and relavance references are written in a clear way that it doesn't affect the traffic engineering of chipset, doesn't effect the physical and software level of parallelism, caches are allocated correctly through methods of file system, partition, or other structure methods of implementation.

So how does this translate ultimately? Well this can affect simple data-orientated presentation, such as presenting a simple graph, a SVG picture, high quality graphics, sharing, middleware communications. Faster method of protocols will also be hard to implant which can dramatically increase the ability to implant security algorithms, data are not easy translated. As time progress with each type of new concept of programming language such as event-driven programming (like application that are firmly concern with things like scheduling), these will decrease the performance, since data values are physical, where object can't really define values clearly such as Zero in one type of math translating to the defintion of Zero in other type of Math. In each program they can, but transfering through a fast standard of The Semantic categorizing fast growing infrastructure, it won't stand a chance.

--Ramu50 (talk) 04:04, 1 October 2008 (UTC)

Add a "Criticism of cloud computing" section?

In The Guardian recently it's been reported that two significant people in the computer industry - Richard Stallman and Larry Ellison - have criticised the concept of cloud computing. Stallman called it "marketing hype", and Ellison called it "fashion-driven" and "complete gibberish" - see here. Should such criticism be included, and if so, how? I would go ahead and just add a "Criticism of..." section myself, but I see the article's protected so maybe the whole concept's a sensitive subject. What do others think?--82.148.54.195 (talk) 11:47, 4 October 2008 (UTC)

I'm in favour of criticism; I think the protection is related to WP:EL abuse rather than anything else. But, I'm not sure that rms's faults are valid. Also, if Oracle are so negative about it, why the recent launch of Oracle-on-EC2, combining Oracle 11g (g for grid) on top of Oracle's RedHat linux derivative, Unbreakable Linux.

Some criticism points are: too vaguely defined to be meaningful. Not a solution to many problems. Creates single points of failure in the infrastructure. For the latter, the S3 outage is a good example; a lot of sites broke when S3 stopped working. However, we really need citable criticisms, instead of inserting our own analysis. SteveLoughran (talk) 14:08, 4 October 2008 (UTC)

I totally disagree what Richard Stallman says, that is a direct-unintelligent comment that is similar to what Pat Gelsinger said about the future of Graphics processing. Yet few month later Microsoft and many other reviews have already debated of that topics. ref

• Moore's Law have been debated as some RAM companies hypothesize transistors might end by 2020 ref
• Intel Atom SCH, shows Intel lack of understanding of how multiplexing device work at all.

Also base on the past reputation of IDF and Intel inability to support bracket USB as a basic knowledge of comoputing, why should anyone believe in that buffoon.

Reading from that topic, I can already see that Richard don't even understand how Cloud Computing can change AJAX to a whole new level and implant parallel computing processor design which can work in sync with Cloud Computing and can dramatically increase the relational database processing. Likewise I think he is like the rest of the amateur who is still getting confused with UML and XML + OO objects and the previous things I just said. The proof is obvious, the article didn't comment anything that shows his understanding of the topic at all. It sounds more like he has an anger / frustration management issue than knowing what he is talking about.

Also the architecture of how a CPU-GPU has already been known to one of the company that make server and workstation CPU which I do not wish to reveal. With that being said, I think a lot of Intel and Microsoft are statements are totally immature and I do not trust their fact at all.

Actually there already been good YouTube videos that explain cloud computing quite well, the only thing is that too many companies right now is sometimes confused and almost reveal their secrets and the idea of cloud computing, so you can't really tell who is going in the right direction.

The fact is too many people right now in the industry is judging things by what is obvious and therefore is conditioned. It is similar what many reviews debate on Solid State products and Hard Drive, yet the only knowledge they use is power and speed. SSD (NAND, SLC or MLC) vs Hard Drive, CPU-GPU +/- programmable codec has, Cloud Computing are all products that havne't fully mature, so even if we are on the right track that doesn't mean you are correct. As other science has proven the just, because you are more "advance" doesn't mean you are the best. As recently the debate of evolution hypothesize that all animals may be all capable of doing the same thing, such as the ability to fly, it is just a matter of how efficiently they can fly. However, just because eagle can fly the best by using soaring, doesn't mean they are a good flyer, if you place them at an enviroment where there is nearly no wind, the feather basically is more heavy. You may say I am wrong, that not everything can perform "anything" they desire, but I am going to telly you that is where you are wrong. Data utilization can achieve that, unforunately very few people that I talk to before know how to utilize it at all due to insufficient knowledge.

More examples are For the past 30 some odd years, speed has already proven us that it is not a future, the ability to efficiently utilize data mangement knowledgeability towards a design is whats important as seen in Celeron, Pentium and Core processors all having speed such as 2.8GHz can have a dramatical difference in the workload. The same as Overclocking the highest speed doesn't gurantee stability in performance.

The reason why I don't want to reveal it, because Intel would go ahead and copy it straightaway, this is not the first time Intel have done it and I totally don't trusted the idoit and unethical practice of Intel as they always do one thing and say the other. As far I am concern, before they say their C2Q is better than Phenom and now they copy it, wtf. For Christ sake, over 15 ads I seen on TV about computers less than 3 ads advertise C2Q while they only advertise Core 2 Duo, yeah so much for the claims that society like to make. Load of crap. --Ramu50 (talk) 22:39, 6 October 2008 (UTC)

Cloud-based version of wikipedia

Is there something like that yet? Nodes would communicate with each other a lot like file sharing applications do now, with articles being the items that were cached locally or searched for. Updates would be an interesting problem, but there is still a decentralization advantage here that could mean decentralizing and open sourcing the very last piece of the pie: the server hardware itself. —Preceding unsigned comment added by Zaphraud (talk • contribs) 00:43, 5 October 2008 (UTC)

I think UML can utilize RPC to achieve that and in some virtualization. Theoretically it is very possible to achieve it, you just need to manage the protocol traffic engineering very well or else leakage would cause havoc that might lead to Data Duplication, faults...etc. --Ramu50 (talk) 22:53, 6 October 2008 (UTC)