I have used couchdb in large systems and small systems. CouchDB is at the end of the day a DB use it as a DB don't embedded your webapp in it.
First Impressions of Sitting a Web App on CouchDB
11–20 of 21 posts
Re: First Impressions of Sitting a Web App on CouchDB
#12You just made my day when you quoted my stackoverflow answer. Thanks, man.
Re: First Impressions of Sitting a Web App on CouchDB
#13From the article: "CouchDB + Another Layer as Web Server is Redundant". This is very true, and the biggest difference to other databases I've used, NoSQL or not. It ends up being a double-edged sword for CouchDB. On the one hand, it saves having to context switch between thinking about the database, thinking about the web server, thinking about the web framework, etc.. For a single developer, this is not to be sniffe…
CouchDB is not as limiting as you suggest but it is a total paradigm shift. There is more to CouchDB than map-reduce.
In my view, CouchDB is more at home as a middleware layer than a database layer.
Take your current project as an example. Why not have Apache reverse proxy to CouchDB? You'd give up zero CouchDB functionality and would gain Kerberos authentication.
Putting another web server in front of CouchDB is unnecessary, but putting web proxy servers in front of it is totally useful. In other words, adding HTTP layers on top of CouchDB means you don't have to trade-off anything.
CouchDB lives and breathes HTTP. If you choose to keep your database from talking with the outside world directly, then CouchDB is a poor choice and you're right to go with MongoDB.
Don't let the name fool you, people. CouchDB isn't simply a place to stuff and retrieve JSON data.
Re: First Impressions of Sitting a Web App on CouchDB
#14I always am annoyed when I read that CouchDB can "scale up and down".
CouchDB has NO internal concept of sharding. The only thing it can do is repliaction. Riak and Cassandra can actually scale up and down, CouchDB can scale up and down as much as MySQL can...
(or did I miss something?)
Re: First Impressions of Sitting a Web App on CouchDB
#15I always am annoyed when I read that CouchDB can "scale up and down". CouchDB has NO internal concept of sharding. The only thing it can do is repliaction. Riak and Cassandra can actually scale up and down, CouchDB can scale up and down as much as MySQL can... (or did I miss something?)
There is a recently open-sourced fork of CouchDB that does the sharding thing. With this addition to the capabilities, CouchDB really can scale up to hundred machine clusters.
Re: First Impressions of Sitting a Web App on CouchDB
#16I always am annoyed when I read that CouchDB can "scale up and down". CouchDB has NO internal concept of sharding. The only thing it can do is repliaction. Riak and Cassandra can actually scale up and down, CouchDB can scale up and down as much as MySQL can... (or did I miss something?)
[deleted]
Re: First Impressions of Sitting a Web App on CouchDB
#17I have used couchdb in large systems and small systems. CouchDB is at the end of the day a DB use it as a DB don't embedded your webapp in it.
I'd say you can do either, depending on your requirements. Some of the biggest CouchDB users use it as a scalable back-end. But some of the most exciting uses are deploying personal web-apps to the desktop.
Re: First Impressions of Sitting a Web App on CouchDB
#18I always am annoyed when I read that CouchDB can "scale up and down". CouchDB has NO internal concept of sharding. The only thing it can do is repliaction. Riak and Cassandra can actually scale up and down, CouchDB can scale up and down as much as MySQL can... (or did I miss something?)
update just found a great article on scaling with CouchDB using Lounge
http://nosql.mypopescu.com/post/683838234/scaling-couchdb
and a company that provides the service Cloudant: https://cloudant.com/
Here's another shard manager project, Pillow: http://knuthellan.com/2010/07/14/feature-prioritization-for-...
I think the design philosophy for couch is keeping smaller pieces of Big Data synchronized. The sum of all those small pieces is like one larger database.
Re: First Impressions of Sitting a Web App on CouchDB
#19You just made my day when you quoted my stackoverflow answer. Thanks, man.
You're great answer helped me better understand the app/DB relationship, and added value to the post. I should be thanking you, in fact I will. Thanks shotgun!
Re: First Impressions of Sitting a Web App on CouchDB
#20Please note the distinction between high availability writes and lock-free writes. CouchDB offers the former.
As I understand you can always write to a node. Where's the lock?