couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filippo Fadda <>
Subject Re: A good introduction to CouchDB and couchapps/webapps
Date Mon, 22 Jul 2013 19:51:45 GMT
Here you can find a books list on the subject:

Beginning CouchDB
CouchDB - The Definitive Guide
CouchDB and PHP Web Development Beginners Guide
Getting Started with GEO, CouchDB, and Node.js
Implementation of a distributed application using the document-oriented database CouchDB
Scaling CouchDB
Writing and Querying MapReduce Views in CouchDB

I think no one of them answers to your question actually, anyway it's a good start.

If you are a PHP developer you might enjoy using ElephantOnCouch client library, actually
the most complete library for CouchDB. The implementation uses alternatively cURL or PHP sockets
(by default), with full support for chunk responses, etc. To use CouchDB with ElephantOnCouch
you don't need to know CouchDB APIs at all, you just relay on the library itself.
ElephantOnCouch suite offers also a query server, EOCServer, that let you write map and reduce
functions in PHP.
You can easily install it using Composer.
The library is not yet official released but you can find it on GitHub:

Documentation can be generated from source using doxygen. The Doxyfile is included.


On Jul 22, 2013, at 3:54 PM, Yves S. Garret wrote:

> Hi, I'm reading the free book CouchDB the Definitive Guide.  It's a good
> intro in some respects, but
> when it comes to building any sort of web applications, it doesn't -- for
> lack of a better term -- hold
> your hand enough.  I understand the advantages of "pushing" your documents
> (and apps) from one
> database server to another, I like that idea.  The one thing that I don't
> understand is how do you go
> from a hello-world example to some silly little blog to something that's a
> more advanced.
> I'd really like more details on this, if someone knows of another book or
> some guide online or point
> out what I'm missing in all of this, I'd greatly appreciate this.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message