<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: CouchDb: document oriented persistence</title>
	<atom:link href="http://www.sitepoint.com/blogs/2006/09/07/couchdb-document-oriented-persistence/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2006/09/07/couchdb-document-oriented-persistence/</link>
	<description></description>
	<pubDate>Fri, 25 Jul 2008 05:38:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: webdevguy</title>
		<link>http://www.sitepoint.com/blogs/2006/09/07/couchdb-document-oriented-persistence/#comment-63873</link>
		<dc:creator>webdevguy</dc:creator>
		<pubDate>Wed, 04 Oct 2006 11:53:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1707#comment-63873</guid>
		<description>This sounds VERY much like the attributes of Lotus Notes but a lot less expensive.</description>
		<content:encoded><![CDATA[<p>This sounds VERY much like the attributes of Lotus Notes but a lot less expensive.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Damien Katz</title>
		<link>http://www.sitepoint.com/blogs/2006/09/07/couchdb-document-oriented-persistence/#comment-52781</link>
		<dc:creator>Damien Katz</dc:creator>
		<pubDate>Fri, 08 Sep 2006 15:42:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1707#comment-52781</guid>
		<description>Wow Harry, I should get you to write CouchDb promo. You get it and really do a great job of explaining this stuff. Better than I can.

Thanks again.</description>
		<content:encoded><![CDATA[<p>Wow Harry, I should get you to write CouchDb promo. You get it and really do a great job of explaining this stuff. Better than I can.</p>
<p>Thanks again.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: HarryF</title>
		<link>http://www.sitepoint.com/blogs/2006/09/07/couchdb-document-oriented-persistence/#comment-52469</link>
		<dc:creator>HarryF</dc:creator>
		<pubDate>Thu, 07 Sep 2006 11:11:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1707#comment-52469</guid>
		<description>&lt;blockquote&gt;
Great writeup Harry
&lt;/blockquote&gt;

Many thanks.

&lt;blockquote&gt;
Looks not so useful...
&lt;/blockquote&gt;

As a prototype, understood. But as a project - where it's headed strikes me as &lt;em&gt;very useful&lt;/em&gt;.

For web developers, being able to replicate databases easily, over HTTP, is a big one. Imagine being able to get yourself 10 cheap hosting accounts from different companies, of the $5/month variety, and running multiple replicating copies of your database in parallel on each, with one more expensive account running a reverse proxy in front of all 10 - assuming the latency between the reverse proxy and the backend servers is not too significant, it's a cheap to run a fault tolerant site. It's worth listening to the podcast to hear Damiens thoughts on offline storage.

Also, as the above example with $_POST attempts to point out, being document oriented may simplify development of certain categories of application. Given that the web is primarily resource / document oriented, using a database engine that reflects that means creating / updating might be as simple as passing through a POST. Much of this ORM / ActiveRecord "joy" falls away.

Another potential benefit would be simplifying search - as all documents are effectively a single "unit" of data, they're easier to index - vs. building a search index out of multiple columns of multiple tables.

To an extent I guess you could say, compared to relational DBs, CouchDb is storing data in a de-normalized form, from which a normalized form can be generated, but the issue of normalization becomes transparent to the code creating / updating the data, hence simplification. That also probably means you can do most writes in a single operation - reduced need for transactions.</description>
		<content:encoded><![CDATA[<blockquote><p>
Great writeup Harry
</p></blockquote>
<p>Many thanks.</p>
<blockquote><p>
Looks not so useful&#8230;
</p></blockquote>
<p>As a prototype, understood. But as a project - where it&#8217;s headed strikes me as <em>very useful</em>.</p>
<p>For web developers, being able to replicate databases easily, over HTTP, is a big one. Imagine being able to get yourself 10 cheap hosting accounts from different companies, of the $5/month variety, and running multiple replicating copies of your database in parallel on each, with one more expensive account running a reverse proxy in front of all 10 - assuming the latency between the reverse proxy and the backend servers is not too significant, it&#8217;s a cheap to run a fault tolerant site. It&#8217;s worth listening to the podcast to hear Damiens thoughts on offline storage.</p>
<p>Also, as the above example with $_POST attempts to point out, being document oriented may simplify development of certain categories of application. Given that the web is primarily resource / document oriented, using a database engine that reflects that means creating / updating might be as simple as passing through a POST. Much of this ORM / ActiveRecord &#8220;joy&#8221; falls away.</p>
<p>Another potential benefit would be simplifying search - as all documents are effectively a single &#8220;unit&#8221; of data, they&#8217;re easier to index - vs. building a search index out of multiple columns of multiple tables.</p>
<p>To an extent I guess you could say, compared to relational DBs, CouchDb is storing data in a de-normalized form, from which a normalized form can be generated, but the issue of normalization becomes transparent to the code creating / updating the data, hence simplification. That also probably means you can do most writes in a single operation - reduced need for transactions.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: RaS!</title>
		<link>http://www.sitepoint.com/blogs/2006/09/07/couchdb-document-oriented-persistence/#comment-52427</link>
		<dc:creator>RaS!</dc:creator>
		<pubDate>Thu, 07 Sep 2006 07:13:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1707#comment-52427</guid>
		<description>Looks not so useful....</description>
		<content:encoded><![CDATA[<p>Looks not so useful&#8230;.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Damien Katz</title>
		<link>http://www.sitepoint.com/blogs/2006/09/07/couchdb-document-oriented-persistence/#comment-52370</link>
		<dc:creator>Damien Katz</dc:creator>
		<pubDate>Thu, 07 Sep 2006 01:19:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1707#comment-52370</guid>
		<description>Great writeup Harry. 

&lt;blockquote&gt;enter CouchDb where (if I’ve understood right) you can “compile” tables from the contents of your raw documents using it’s fabric formula language. Assuming the processing done to create the tables is reproducible, replicating databases across systems would then “only” be a matter of copying the raw documents.&lt;/blockquote&gt;

Yup, nailed it, that's pretty much exactly how it meant to work.

Over the next few weeks I'm going to cook up a few more demos to what kinds of applications can be built on this system.</description>
		<content:encoded><![CDATA[<p>Great writeup Harry. </p>
<blockquote><p>enter CouchDb where (if I’ve understood right) you can “compile” tables from the contents of your raw documents using it’s fabric formula language. Assuming the processing done to create the tables is reproducible, replicating databases across systems would then “only” be a matter of copying the raw documents.</p></blockquote>
<p>Yup, nailed it, that&#8217;s pretty much exactly how it meant to work.</p>
<p>Over the next few weeks I&#8217;m going to cook up a few more demos to what kinds of applications can be built on this system.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: HarryF</title>
		<link>http://www.sitepoint.com/blogs/2006/09/07/couchdb-document-oriented-persistence/#comment-52332</link>
		<dc:creator>HarryF</dc:creator>
		<pubDate>Wed, 06 Sep 2006 21:53:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1707#comment-52332</guid>
		<description>Just ran into &lt;a href="http://takingnotes.openntf.org/blogs/takingnotes.nsf/dx/taking-notes-episode-23-06.07.06.htm" rel="nofollow"&gt;Taking Notes Episode 23: 06.07.06 - CouchDb with Damien Katz&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Just ran into <a href="http://takingnotes.openntf.org/blogs/takingnotes.nsf/dx/taking-notes-episode-23-06.07.06.htm" rel="nofollow">Taking Notes Episode 23: 06.07.06 - CouchDb with Damien Katz</a></p>]]></content:encoded>
	</item>
</channel>
</rss>
