CouchDB Vs MongoDB

ikorsakoff:

real world examples; fine presentation

4 notes

hasen: Why I'm choosing CouchDB

hasenj-dev:

Note: I’ve made some edits and added a little extra section about clustering at the end.

I’ve always hated SQL, so I’ve always found the nosql movement pretty interesting. There was a point in my programming “career” where I was very much into python and javascript and json and all the dynamic…

Nuno Job — nano - minimalistic CouchDB client for nodejs

gcman105:

Nuno Job — nano - minimalistic CouchDB client for nodejs June 19, 2012 at 06:27PM

myNoSQL: Riak Performance of Link Walking vs MapReduce

nosql:

If you are asked to compare (or you just wonder about) the performance of link walking and map-reduce in Riak keep in mind the following details of how the two mechanism are implemented:

The biggest difference I see is that the link-walk uses an Erlang function where your MapReduce query uses…

1 note

Getting Started with CouchDB - O'Reilly Media

Getting Started with CouchDB Extreme Scalability at Your Fingertips

By MC Brown

Publisher: O’Reilly Media

Released: January 2012

Pages: 82

0 notes

CouchDB - der RESTful Dokument Datenbank Server

Doodle-Anleitung / Doodle-Tutorial

27 notes

Interesting Data Sets and Tools: Monthly Twitter Activity for All Members of the U.S. Congress

nosql:

Drew Conway:

Today I am pleased to announce that we have worked out most of the bugs, and now have a reliable data set upon which to build. Better still, we are ready to share. Unlike our old system, the data now lives on a live CouchDB database, and can be queried for specific research tasks. We have combined all of the data available from Twitter’s search API with the information on each member from Sunlight Foundation’s Congressional API. […] But be forewarned, working with this system and CouchDB requires a mature understanding of several tools and languages; including but not restricted to; curl, map/reduce, Javascript, and JSON. And that’s before you have even done any analysis.

Original title and link: Interesting Data Sets and Tools: Monthly Twitter Activity for All Members of the U.S. Congress (NoSQL database©myNoSQL)

5 notes

Building an anonymous cloud database - blog.nodejitsu.com - scaling node.js applications one callback at a time.

..

Basic strategies in building a decentralized and anonymous database

  • No central servers. A central server is a central point of failure.

  • No central authorities. A central authority over control of the database indicates another ( and much worse ) central point of failure.

  • Ability to encrypt and obscure data.

  • Ability to run in any combination of local / cloud / hosted. The database should be able to run locally, on hosted servers, and in the cloud.

    • Ability to easily share and replicate data. The data should be able to easily transfer and replicate between multiple systems and users.

..

Apache CouchDB - Ohloh
1 note

CouchDB Buch Website

andywenk:

Moin Moin,

Till Klampaeckel und ich haben ein Buch über CouchDB geschrieben. Es ist im Galileo Computing Verlag erschienen. Till hat ausserdem eine coole website mit vielen Informationen, Code und Links zum Buch erstellt. Einfach mal hier gucken:

http://www.couchdb-buch.de

Cheers

Andy

(Source: andywenk)

CouchDB roundup · romangeber.com

Quite some time has passed since I started having fun with CouchDB. After using the usual PHP/MySQL Combo for more than a decade now, I’m quite used to the thought of using a three layer model to build web applications. I was so blinded by that “usual” procedure that I didn’t even think about it any other way.

Factual API Powered by Node.js and Redis

nosql:

Continuing my search for non trivial node.js + NoSQL database application, here’s Factual stack for serving their API:

Factual API Stack

Factual architectural components:

  • Varnish
  • HAProxy
  • Node.js
  • Redis
  • Solr

Why Node.js?

We chose Node because of three F’s: it’s fast, flexible, and familiar. In particular, the flexibility is  what allowed us to use our Node layer to handle things like caching logic and load balancing, in addition to the aforementioned authentication and authorization. To make our Node layer scalable, we use multiple instances of Node tied together with Redis to keep things in sync.

Also worth mentioning is that data served through Factual API is always JSON, so having a server side JavaScript engine alsa takes reduces the need for converting data to different formats.

Original title and link: Factual API Powered by Node.js and Redis (NoSQL database©myNoSQL)

9 notes