CouchDB: Roll Your Own, Or Go With a Service?
Nerval's Lobster writes "Developer and editor Jeff Cogswell asks: When it comes to implementing a CouchDB installation, do you roll your own, or go with a service that provides a hosted version of the database? He takes a look at some of the technologies present in CouchDB that can greatly influence that decision. His conclusion? Like all things, it's a little complicated. 'If you're going to be self-hosting—unless you're working on a really small system—don't use the basic CouchDB for anything,' he writes. 'If you want scalability, either go with Couchbase or BigCouch, or wait until Cloudant's BigCouch merger into CouchDB is officially available.' But going with a host also creates its own things to watch for, including potential issues with replication and eventual consistency."
And maybe a handful of Excel sheets, but only if you have lots of data.
How many couches do you people own that you need to create a database for them?
But is it webscale like MongoDB?
Make sure Cosmo Spacely doesn't find out.
Unless the host you choose is within 5-10ms of your server network-wise you should always self-host.
An average site makes many queries per page to the database. The latency adds up fast. People often fail to understand this and end up with very slow sites and/or very frustrated developers.
TFA being hosted on slashdot.org en being unreachable, we are led to the conclusion that /. /.-ed itself. Hooray !
Religous speak to God. Insane are spoken to by God. When all shut up, one can finally hear Shostakovich in peace
What's a CouchDB? This seems like a niche subject without any description..
This space for rent, inquire within.
I have a serious question: who really uses CouchDB? From everything I've read and experienced, it's a horribly slow database that can't scale worth a damn (much like most databases today--seriously, it's 2013, why hasn't anyone figured out how to easily scale/shard) and then layered on top of a clunky map/reduce query interface.
The only interesting thing about CouchDB is the ability to easily write APIs thanks to its HTTP interface.
This could be a very compelling business model. Instead of producing physical goods like sofas and counches one could project them virtually using holograms and force fields. Couch service providers would be able to offer a wide array of couches virtually as a service. However I suspect if you fail to pay your bill on time your couch may become incresingly uncomfortable to sit in.
No.
Aside from the name and the founder, there is very little in common between CouchDB and Couchbase.
I'm pretty sure that Couchbase is initially being built around memcache.
Is if you want a database that handles syncing back up after being offline for a while. Has some use for embedded and syncing in that regard with a minimal resource footprint. Outside of that particular use case, its not a good choice for much of anything.
If whatever you're building is large enough that you think you're unable to host your own small NoSQL database, is it time to reconsider using a small NoSQL database?