From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NmXst-0005AT-Q0 for garchives@archives.gentoo.org; Tue, 02 Mar 2010 19:36:00 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DECC0E0EC2; Tue, 2 Mar 2010 19:35:35 +0000 (UTC) Received: from mail-bw0-f219.google.com (mail-bw0-f219.google.com [209.85.218.219]) by pigeon.gentoo.org (Postfix) with ESMTP id 9F34FE0EC2 for ; Tue, 2 Mar 2010 19:35:35 +0000 (UTC) Received: by bwz19 with SMTP id 19so560534bwz.26 for ; Tue, 02 Mar 2010 11:35:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=6uubj/M/ohfEjgKZK0ZrR2BMUjaEdUY79ik25MEr8IY=; b=O/PuAlQzeREj8sq0eQyNJbO+yytjQDccUFWGQf7RqXcC5PX/PQbAnovqYE17OxcuaM PbMO1EjWWo5WLSeKU42ys5+6T2jHzUDF6waYOHRYDExXABY6z6R46afgEFGoDJlmkc7Y +M0IshQJpl/v4uuBjo3kHO+Rl2l3Y6D2LbDUs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=KCPDFAX2YTx5aBnAjtUeMZcP4scssWKu7n09vhkhkwAFaqCZQhjOB4eilUN9j7MFwp HN22peV47JG4uxyHSNDdS4snJvEbeyw0JCihVuzDoxFvzH8s1LUNeNWyAO5PY45dmO+U 0qrF1D7Df9EOMylwoBKzHGRHrbb3hzMTL+PpA= Received: by 10.204.24.139 with SMTP id v11mr1228761bkb.121.1267558534880; Tue, 02 Mar 2010 11:35:34 -0800 (PST) Received: from nazgul.localnet (196-210-238-8.dynamic.isadsl.co.za [196.210.238.8]) by mx.google.com with ESMTPS id e18sm2583058bkd.20.2010.03.02.11.35.32 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 02 Mar 2010 11:35:33 -0800 (PST) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: [OT] NoSQL? Date: Tue, 2 Mar 2010 21:33:00 +0200 User-Agent: KMail/1.13.0 (Linux/2.6.32-zen6; KDE/4.4.0; x86_64; ; ) References: In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201003022133.00869.alan.mckinnon@gmail.com> X-Archives-Salt: 1b1ee93f-3cc5-40ea-8a74-1a52874e4dfe X-Archives-Hash: 38416243e1f64f8cb4adc54f37c98113 On Tuesday 02 March 2010 19:07:21 walt wrote: > On 03/02/2010 04:23 AM, Arttu V. wrote: > > On 3/2/10, walt wrote: > >> This article was a big surprise to me. Am I the last one to hear about > >> this stuff? > >> > >> http://news.cnet.com/8301-13505_3-10461670-16.html?part=rss&subj=new > >> s&tag=2547-1_3-0-20 > > > > If you're expecting a discussion then perhaps you'd care to narrow it > > down a bit: which part of the article are we expected to feel > > surprised about? > > I was surprised that three major social networking sites have dumped > MySQL (but now the article says only two sites). I've also not heard > of the "NoSQL" movement before, and I'm curious to know what's motivating > it. Maybe nobody trusts Oracle? Because Codd's relational database model, as implemented by Oracle, Sybase, PostgreSQL, MSSQl and a slew of others, is not the only way to model a data storage system (aka database). In much the same way that a bakkie with a canopy is not the only way to transport workers, as buses do exist. Relational databases are demonstrably mathematically correct, but like all things they have their limits to how far they can scale. More often than not, this limit is imposed by how fast the db engine can access and identify data using the hardware upon which it is built. Traditional RDBMSes don't even vaguely scale to the levels Facebook runs at. The NoSQL movement is nothing more than an effort to find other ways of extracting data having consciously ditched SQL for the job. By way of example (this is not NoSQL per se, it illustrates the point), Google's data extraction methods are not even remotely SQL. Heck, they aren't even completely correct, they are merely "good enough". See what happens when you dump the old mind-set and look at fresh new ideas? Oftentimes you get something that works better than the old way. Google does not care that their search results are not 100% spot on, they are good enough for your query. If other stuff that they missed deserves to be higher in the ratings, it will climb higher over time till it does show. Considering the size of Google, this is a very workable approach. -- alan dot mckinnon at gmail dot com