Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of adamjpetty@gmail.com
 designates 209.85.220.20 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=KGW7JGGBqUAH+tLCxSag4qhsUNZ2KtlUBC3NCiDQ+49ff5+0reB8Waxa4Bt0wM5dt5
         Z9Zhv42b55wrNNB44Wqik9D9QNMifKoOETf0QPhRWLQ+CoNiMWGb5Yps2CenARMNxonV
         dlU9i/PMf5LGeLt9VIh2zBrrf4Z9s8lL6yWZg=
MIME-Version: 1.0
In-Reply-To: <20090209152738.GS21180@tumbolia.org>
References: <5186956f0902082052m43546a8dmb6d9a3ebf9685034@mail.gmail.com>
	 <5186956f0902090228p5a6db266l764fde4c82b571d0@mail.gmail.com>
	 <5186956f0902090338i2829df1erebaa24a4feea7e06@mail.gmail.com>
	 <5186956f0902090449s76befd76g4cf9ded9f59efc86@mail.gmail.com>
	 <5186956f0902090627y1239b12es505ee80b2d6bd248@mail.gmail.com>
	 <6a8c90ba0902090651q258bb335uf6142ccb25261931@mail.gmail.com>
	 <20090209145701.GR21180@tumbolia.org>
	 <2B705A9C-441C-487C-95E7-B537682F49A7@cisco.com>
	 <20090209152738.GS21180@tumbolia.org>
Date: Mon, 9 Feb 2009 10:55:25 -0500
Message-ID: <6a8c90ba0902090755i575bc907qcc35b62e4d7c80b1@mail.gmail.com>
Subject: Re: [user] Re: The Blog
From: Adam Petty <adamjpetty@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=001636c5b4dd26d60704627e6679

--001636c5b4dd26d60704627e6679
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Well -- Its sounds like couch is starting to be able to stand up to the
fire... which is why I'm digging this thread.

But yes - too much heat and the whole proprietary/RDBMS community could
start aiming bazooka's at it - which might do some damage.  So maybe some
middle ground somewhere..

I'll work on a compilation - and post it and see where the wiki takes it.  I
would have to agree that there is something to google's jedi strategy with
microsoft...

"nothing to see here... these aren't the droids you're looking for... of
course we're not competing with microsoft"

-- and can keep that in mind also

okay enough about that -

Just as a frame of reference... the only thing that has held couch back for
development at my work - has been the lack of a pluggable reporting tool.  I
know that is really just semantics - that Pentaho can use an XML dataset -
and JSON - XML translation seems easy BUT.... nothing out of the gate yet.
In my case - bosses love names -- SSRS, 10g, CrystalReports, Business
Objects..etc.

-- as for an example db issue...
For some reason -  without transactions the RDBMS people at my work seem to
not want to consider couch for anything having to do with money.

I know it would be fairly simple to have an "accounts" array field on a JSON
user-account document - that way no single "enities" account could be
changed by more than one write at the same time... seems rediculously simple
- but is there a case where this could fail?

Seems like money is always the most sensitive issue - if we could develop a
very usable "banking" example db secenario - maybe an artificial bank app?
and see if we can break it - or get out of sync balances due to timing
issues -- etc?

.02$


On Mon, Feb 9, 2009 at 10:27 AM, Noah Slater <nslater@apache.org> wrote:

> On Mon, Feb 09, 2009 at 04:18:09PM +0100, Wout Mertens wrote:
> > To be honest, I think saying RDBMS and CouchDB are for different
> > solutions is just you guys being nice. I think that any application
> > would benefit from using the CouchDB model and only in very specific,
> > very demanding cases an RDBMS would be better. I can't think of any
> > examples though.
>
> Not really, I just like avoiding the flames. Heh heh.
>
> I see where you want to go with this, and I agree that some applications
> are
> better suited to CouchDB, but I think it's often a blurry line, and you
> will
> draw fire from the RDBMS people for anything too concrete.
>
> --
> Noah Slater, http://tumbolia.org/nslater
>

--001636c5b4dd26d60704627e6679--