At the time I have covered MongoDB 1.4 release I was noticing the community excitement around its geospatial support. A similar initiative was started two years ago to bring geo support to CouchDB:
Why should someone want to put his geodata into a big mess of thousands of documents instead of a nicely structured RDBMS? You don’t have to be a computer scientist to know that retrieving data out of a RDBMS is damn fast and a DODB approach sounds like a slow, “I grep through a long list of files”.
This might partly be true, but high performance shouldn’t be a use case for DODBs. Their flexibility and ease of usage is what they make them perform great. You have the choice between being fast or being flexible.
and now ☞ GeoCouch is here:
An idea has become reality. Exactly two years after the blog post with the initial vision, a new version of GeoCouch is finished. It’s a huge step forward. The first time the dependencies were narrowed down to CouchDB itself. No Python, no SpatiaLite any longer, it’s pure Erlang. GeoCouch is tightly integrated with CouchDB, so you’ll get all the nice features you love about CouchDB.