Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of ryan.ramage@gmail.com
 designates 209.85.212.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <2C65B131-0A72-4F45-936E-6CE413CFFC1C@gmail.com>
References: <4EB80D11.1080504@gmail.com>
	<F7F0E7B6-E08B-43E4-A073-664FCEF0B606@gmail.com>
	<4EB95D32.7010505@gmail.com>
	<48DFA539-4203-41F9-AB4A-D6DDEC9763BD@gmail.com>
	<CAL-h1aSFiymJMUJpfxza8EO3SgXiVpT6RXnXUr-2X+ZSfUD=AQ@mail.gmail.com>
	<2C65B131-0A72-4F45-936E-6CE413CFFC1C@gmail.com>
Date: Tue, 8 Nov 2011 11:37:26 -0700
Message-ID: 
 <CAL-h1aQgCS9_4fy=oi1cdKEX2iet+jts60egfxgf5WES-6OphA@mail.gmail.com>
Subject: Re: nodejs couchapp
From: Ryan Ramage <ryan.ramage@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

> Sometimes it's easy to forget how much of building couchapps is simple be=
cause CouchDB is simple, and writing an app in node.js with CouchDB as a da=
tastore is still quite simple even if it's a little more complicated than a=
 couchapp and as you start doing those backflips it might be simpler to bre=
ak out of the couchapp model and keep CouchDB as a backend store.
>

I totally agree. But I think most developers tend to try and find the
biggest box to use. So when they look at couchapps they go hmm, nope,
not going to try, not a big enough box.

What might be useful to explore is some docs/best practices for
growing your app out of the couchapp box. "How should I migirate
assets into a node front end?", "What about auth", etc. That way
people can feel comfortable starting with couchapps knowing they can
move upwards if needed.

Maybe I have not investigated if such resources exist, but it might be
useful for the various couchapp communities to provide.

Ryan