Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: marketing@couchdb.apache.org
Received-SPF: pass (nike.apache.org: message received from 54.76.25.247 which
 is an MX secondary for marketing@couchdb.apache.org)
MIME-Version: 1.0
In-Reply-To: <0B891CED-B735-4D86-86D2-1C4CDF6BDE21@apache.org>
References: 
 <CAPMhwa5R6CdeQP-m_FHfqYsJ4NDwLYiePuwrsi2bRfzifncRpw@mail.gmail.com>
	<CAHw0XrtCxKWzM5x9Q2XjqxV3HOPLKCyOuTVOpMOeJKobJCzs5g@mail.gmail.com>
	<CAPMhwa7KTf4QTYm5HKyG2TxAzYPJ4a5CxAg90v8A26gY=W7poQ@mail.gmail.com>
	<CAHw0Xrt=1zvX9ud_Dezmks6jP10kPWMp08qXqO2ohO9yWCi2pw@mail.gmail.com>
	<CAPMhwa4XzFmPEdWRTdrtQW4x4thXcsCMe-OrJyA81OfL8DMTEQ@mail.gmail.com>
	<CAHw0XrtWiqQbQdaYoGGrjK2kGthJHeqTKg6K-EzzqfOe0rVycg@mail.gmail.com>
	<33BD4D82-787C-48D5-B963-FEEA4C0913CB@apache.org>
	<CADA9kr_7X6ha_hK3qb7N4FLDKeXCUQ7kDnYxN86Vzs_mRLKeCg@mail.gmail.com>
	<4209351E-F51E-4DB5-8A5F-8AB53DA21877@apache.org>
	<FAB68F13-D72C-45D0-8BD2-3E5D2F85CFF2@b2w.com>
	<0B891CED-B735-4D86-86D2-1C4CDF6BDE21@apache.org>
Date: Wed, 6 May 2015 08:47:41 +0200
Message-ID: 
 <CAPMhwa7mq5U5HoVEd=fZRMoOpaisGs69PzztPQaVaE6KvMMxUw@mail.gmail.com>
Subject: Re: How do CouchApps fit into the CouchDB story? (Was: CouchDB
 Articles, Pills and Tutorials Ideas)
From: Giovanni Lenzi <g.lenzi@smileupps.com>
To: marketing@couchdb.apache.org
Content-Type: multipart/alternative; boundary=047d7bdca97ce8bb550515642bf7

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

@ermouth
> http://cloudwall.me/etc/json-editor.html =E2=80=93 gonna make it couchapp=
 editor,
AWESOME... cloudwall already deals with documents and attachments, so you
are already probably not too-far ahead.. That would be awesome!!  That
could really dramatically increase adoption-rate, by making CouchDB the
first platform-independent and browser-only development environment for
secure web applications.

@jan
> - a lose collection of features inside CouchDB that all have problems:
> - rewrite: not flexible enough, web devs expect more options for routing
Sorry... but Flexibility is probably the number one feature of Couchapps
and rewrite handler. Also the complete independency between 3 layers:
presentation, business logic and data provides huge development benefits..
it's not only academic definition
https://www.smileupps.com/couchapp-tutorial-chatty#simplifieddevelopment
https://www.smileupps.com/couchapp-tutorial-chatty-couchapp-design#chattyap=
idesign
https://www.smileupps.com/couchapps

Moreover Couchapps have system administration benefits other approaches
simply lacks:
- enable system wide queries, essentials to real-word scenarios: like a
simple "how many users have done that today?".. how can you do this type of
query, and how practical it is with a "database-per-user" approach?
- depending on your use case and the size of your data.. you can split data
into single or multiple databases for historical purposes(a database per
month/year) or depending on data type.. withouth the drawback of
exponential and uncontrollable growth typical of "database-per-user"

With this I'm not saying "database-per-user" is bad.. on the contrary, it's
VERY GOOD especially when data belongs to his own creator, thus for
offline-first and nobackend. PouchDB and Hoodie usefulness won't be
affected in any way by leaving Couchapps. On the contrary they can only
benefit by Couchapp features too, like security.

--047d7bdca97ce8bb550515642bf7--