Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of engelster@gmail.com
 designates 209.85.212.178 as permitted sender)
MIME-Version: 1.0
Date: Tue, 8 Apr 2014 13:45:33 -0500
Message-ID: 
 <CAFf7Ch1tecvYAc+d71e=HE5B6OW0EwZhm8tv=D=VqYs-deTaOw@mail.gmail.com>
Subject: Would this be a sane use case for couchdb?
From: Der Engel <engelster@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=f46d043c08649e321d04f68c6308

--f46d043c08649e321d04f68c6308
Content-Type: text/plain; charset=ISO-8859-1

Hi, I'm a newbie trying to write his first real web application, couchdb
has interested me because of its http api and the thing that the data
model/structure of data of the app would probably be changing over time.
The webapp is going to be a invoicing software for certain niche,  so I
guess I probably need a DB were transactions are reliable and data
integrity is very good. I don't intend to run a cluster at first, but it
may become a necessity later on.

Would CouchDB be a good fit for this kind of application?

Thanks,
Der

--f46d043c08649e321d04f68c6308--