Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 84506 invoked from network); 26 Dec 2008 14:31:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Dec 2008 14:31:31 -0000 Received: (qmail 16643 invoked by uid 500); 26 Dec 2008 14:31:26 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 16583 invoked by uid 500); 26 Dec 2008 14:31:25 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 16572 invoked by uid 99); 26 Dec 2008 14:31:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Dec 2008 06:31:25 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pablo.platt@gmail.com designates 64.233.182.189 as permitted sender) Received: from [64.233.182.189] (HELO nf-out-0910.google.com) (64.233.182.189) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Dec 2008 14:31:19 +0000 Received: by nf-out-0910.google.com with SMTP id d3so458477nfc.25 for ; Fri, 26 Dec 2008 06:30:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=hixIksuYuUgW5c+fNulZGc88NmI9kjEm+OR68gPzLS8=; b=qEsEF8zjcU/tpDjaN02CAVDklNP76ZPpYg2o6hxPSc1byUsGE7V95UwHI7kuk2qojg GiktzlliXATuwP8PJA3qimEVcCquAaTk8EMvyK6r8dgdjsL8yV9ynmITxjQ+yV5Oj9IX RB6oZxekRsGqvs18B/LiKEjKtMI0JnWZAWaEY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=U2F5JXeLl6gQKuCtXcGG4+feuSzBhQRqpCE6wVRHplNk9tqUD1KJa0NNi/ho/Spx+4 wpb97zAMxLbSSGjlDGbju0mlbgWgvbNs4BlsIRXxDWmVhVvAm54hvbhbuRE058yG2ErS czwCYwE2kqb7gVCiZ7b31Taug/CUnmzugt/Uc= Received: by 10.210.20.17 with SMTP id 17mr12597782ebt.37.1230301857338; Fri, 26 Dec 2008 06:30:57 -0800 (PST) Received: by 10.210.128.8 with HTTP; Fri, 26 Dec 2008 06:30:57 -0800 (PST) Message-ID: <186b32bc0812260630m36835e2did7a67954a98b1a90@mail.gmail.com> Date: Fri, 26 Dec 2008 16:30:57 +0200 From: "pablo platt" To: user@couchdb.apache.org Subject: use cases MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_117333_33015218.1230301857321" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_117333_33015218.1230301857321 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, I've read allot about couchdb but still trying to understand what are its use cases, and if I can use couchdb alone for projects or do I have to combine it with relational db. Database for an instant messenger server. Obviously couchdb will be good at logging chat rooms and maybe contact cards with arbitrary data. Will it be good for handling user credentials, roster(contact list) and session management? Database for a social network. Again, couchdb is good for handling blog posts and messages between users. Will it be good for handling connections between users (social graph), permissions, settings...? On thing that is very appealing to me is that a client can access the db directly for both read and write operations without putting load on the application server. I wonder how far couchdb's authentication and permission implementation can go with that. If I understand correctly, a user need to add his credentials to each request which is not very secure. Can I use some kind of SASL and session management (Cookie or session id)? Are the couchdb permissions all or nothing? For example, can I limit the size and number of documents a user can create? Thanks ------=_Part_117333_33015218.1230301857321--