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 marcello.nuccio@gmail.com
 designates 209.85.214.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <8B350540-5545-4983-9413-68BB920ABC67@supercoders.com.au>
References: <8B350540-5545-4983-9413-68BB920ABC67@supercoders.com.au>
Date: Tue, 12 Jul 2011 03:18:59 +0200
Message-ID: 
 <CAMWZAjnkpfRXxJSpS96V8s9Btg0VfhYxbP2xMjZy7UTmWx99Yw@mail.gmail.com>
Subject: Re: Building substantial "pure" 2 tier CouchApps - feasible?
From: Marcello Nuccio <marcello.nuccio@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I am building a pure couchapp to:
  - insert the orders of the clients;
  - insert the modifications requested by the clients;
  - assign the work to the laboratories;
  - track the warehouse.
  - etc.

Not very big, but quite complex because I have many document types and
I must exchange data with lot of legacy systems.

It is an hard work if you are used to RDMS. The most challenging problems a=
re:
  - how to model the data to keep the couchapp simple, efficient, and
easily interoperable with other system?
  - access control: in CouchDB is a brand new world. Everything you
already know on access control is almost useless with CouchDB.
  - you will need to write some external utility to do some tasks, not
only for maintenance.

just my 2cents...

Marcello

2011/7/12 Andrew Stuart (SuperCoders) <andrew.stuart@supercoders.com.au>:
> I'd like to build a rather substantial application, it would be nice to
> build it as a pure 2 tier CouchApp.
>
> How practical is this really? =C2=A0Does anyone have experience building =
anything
> big in this way? =C2=A0Or are 2 tier CouchApps really only effective for =
small
> stuff?
>
> I understand that it very much depends on what the app does, but I'm tryi=
ng
> to get a general sense of it.
>
> If pure 2 tier CouchDB apps is an impractical goal then we'll design the
> architecture from the beginning as a 3 tier app and whack in some sort of
> server.
>
> as
>