as a co-founder of Couchbase I should be able to give you a clearer understanding. I’ll take your questions in turn. 1) Correct. Couchbase Server is not CouchDB. It sacrifices some of the neat things CouchDB does (HTTP interface, master/master replication) so it can do other neat things (sub-millisecond latency, gigantic clusters.) In the long … Read more
The CouchDB Guide has a good discussion of pagination, including lots of sample code, here: http://guide.couchdb.org/draft/recipes.html#pagination Here’s their algorithm: Request rows_per_page + 1 rows from the view Display rows_per_page rows, store last row as next_startkey As page information, keep startkey and next_startkey Use the next_* values to create the next link, and use the others … Read more
Get the revision number of the document to be updated if there is a conflict during attachment and recursively call in-case of a conflict, $url = “http://couchdb/DATABASE/DOCID/ATTACHMENTNAME?rev=$rev”; curl_setopt( $ch, CURLOPT_RETURNTRANSFER, true ); curl_setopt( $ch, CURLOPT_PUT, true ); curl_setopt( $ch, CURLOPT_URL, $url ); curl_exec( $ch );
I think that currently, the whole idea of NoSQL data stores and the concept of document databases is so new and different from the established ideas which drive relational storage that there are currently very few (if any) best practices. We know at this point that the rules for storing your data within say CouchDB … Read more
I’ve actually used both pretty extensively, both for very different projects. I’d say they are equally well suited for the requirements you list, however there are quite a lot of differences between the two. IMO the biggest is their query-ability. CouchDB doesn’t have ‘queries’ in the RDBMS sense (select * from …) but instead uses … Read more
We have been using CouchDB for that, saving images as an “Attachment”. But after a year the multi-dozen GB CouchDB Database files turned out to be a headache. For example CouchDB replication still has issues if you use it with very large document sizes. So we just rewrote our software to use CouchDB for image … Read more
Its a late answer, but do check out Hammock. It’s active and going into production use on several projects soon and is receiving regular updates and fixes. Besides basic object persistence, Hammock gives you: True POCO. You don’t even need an ‘id’ property; Hammock tracks that internally. Robust support for views, including an easy to … Read more
After 18 Months of prototypes, testing and waiting for CouchDb to get ready we moved an internal application over to CouchDB in December 2008. So far I’m very happy with that move. It gets rid of a lot of filesystem objects for us (PDFs and JPEGs, now stored as attachments in CouchDB). This enables us … Read more
I recently attended the NoSQL conference in London and think I have a better idea now how to answer the original question. I also wrote a blog post, and there are a couple of other good ones. Key points: We have accumulated probably 30 years knowledge of adminstering relational databases, so shouldn’t replace them without … Read more
nathvarun gave a very complete answer, but I’d like to share the steps I do for authentication in my app. Send email + password via ajax to the server Generate a token in the server and send it back to the app Store email + token in localStorage For every single request I make to … Read more