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.
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.
What's a CouchDB? This seems like a niche subject without any description..
This space for rent, inquire within.
They're, obviously...
You my friend have reached the "golden age" in IT. I can tell so by your sub 1m UID. CouchDB is only arcane to old farts who no longer understand the things the younger crowd finds as "in"
We're from the days when MySQL was getting stored procedures, UDFs and views. That's all old hat. Now databases have Couches, and probably ottomans and coffee tables as well.
Embrace your golden years and die out quietly like the rest of us.... :)
Do not meddle in the affairs of sysadmins, for they are subtle, and quick to anger.