incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Max Ogden <>
Subject Re: to CouchApp or not to CouchApp
Date Mon, 01 Aug 2011 18:14:53 GMT
couch has a pretty full featured security model actually:

and you can proxy couchapps behind a vhost (thus making the rest of the
couch api inaccessible):

and heres a couple 'pure' couchapps i've built lately to help you get a feel
for the stuff possible:



On Mon, Aug 1, 2011 at 2:10 PM, Gregor Martynus <> wrote:

> I had some discussions on the CouchConf last Friday about the pros & cons
> of
> 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
>   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
> same
>   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.
>   1. security:
>   CouchApp comes with build in signup/signin, but what keeps users to
>   access pages like »/db/_all_docs?include_docs=true« ? 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.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message