Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
Date: Mon, 1 Aug 2011 11:10:08 -0700
Message-ID: 
 <CA+5KyPSE3BULUc7KONgx8ZqfNKW++_r8vgdhh7HLxLr0JgfM0A@mail.gmail.com>
Subject: to CouchApp or not to CouchApp
From: Gregor Martynus <gregor@martynus.net>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=000e0cd4b31c9f95cc04a9758ad7

--000e0cd4b31c9f95cc04a9758ad7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I had some discussions on the CouchConf last Friday about the pros & cons o=
f
a CouchApp vs. a traditional 3 tier architecture. I'm new to CouchDB myself=
,
I don't have strong opinions yet. My thoughts so far

PRO

   1. portability:
   a CouchApp has both application logic and data in the same module.
   Together with its replication features one could very easily take the sa=
me
   app used for a web app and put it into a mobile phone or an enterprise
   intranet/extranet.
   2. simplicity / reach:
   It empowers a lot of UI Designers/Developers to build Database backed
   applications. That's pretty impressive, you know jQuery? You can build
   couchApps.

CONTRA

   1. security:
   CouchApp comes with build in signup/signin, but what keeps users to
   access pages like =C2=BB/db/_all_docs?include_docs=3Dtrue=C2=AB ? There =
is now way to
   hide documents created by User A from User B with CouchDB's build in
   features as far as I understand it.
   2. scaleability:
   there are more possibilities to scale with a 3 tier architecture than
   there are for CouchApps

What do you think? Do you have a CouchApp running today in Production?
What's your experience so far?

I'd be happy to summarize the opinions and put them up on the couchDB wiki
so that everybody can benefit from it.

--000e0cd4b31c9f95cc04a9758ad7--