Re: [cville] Re: An Evening with CouchDB
- Matt Dawson
- 2010-03-11 @ 05:03
And here are a few broad conclusions I came to or things I learned.
Some points may be under-informed or flat-out wrong.
1) CouchDB rules at massive replication - especially in a scenario
where nodes can expected to be on or offline at random.
2) MongoDB has an interface that would make MySQL command line users
feel right at home.
3) Both are JSON-tastic. That is, data is returned in that format. We like this.
4) There's probably a library for both in your language of choice.
5) Do you like curl (ie. RESTful architectures)? You'll love CouchDB.
6) MongoDB has (what appears to be a useful) abstraction layer between
your database and the documents contained within. They call these
"collections." To get something similar from Couch, you'd probably be
looking at using a view's map function to chunk your data and the
using reduce for subdividing the data further.
What am I missing?
On Wed, Mar 10, 2010 at 10:03 PM, Ron DuPlain <firstname.lastname@example.org> wrote:
> On Mon, Mar 8, 2010 at 2:43 PM, Ron DuPlain <email@example.com> wrote:
>> Matt Dawson and I are meeting Wednesday (Mar 10) evening to get into
>> CouchDB, 6-8pm at OpenSpace.
> For those who couldn't make it, we had 5 people there. We mostly
> looked at CouchDB, though we did a little MongoDB, and discussed the
> difference between the two.
> We covered, for CouchDB:
> * couchdb-python (and web.py in Matt's example)
> * basics of document interaction
> * interaction via curl (CouchDB is entirely RESTful)
> * interaction via the built-in admin interface, Futon
> * replication
> * stand-alone apps which are stored in the database, couchapp
> * CouchDB installed on an Android G1 with debian
> For MongoDB, we downloaded, ran MongoDB, and launched the mongo shell
> for some hello-world interaction. We had a fairly lively discussion
> about the difference between the two. I'll leave it to the others to