3 ms·
When criticising CouchDB, don't forget about its killer features: Replication: slave, master, multi-master, pull, push, single, continuous over http(s), you na
by js4all 13y ago
When criticising CouchDB, don't forget about its killer features:
Replication: slave, master, multi-master, pull, push, single, continuous over http(s), you name it.
Update handlers: You don't have to fetch, modify and save in every case.
MVCC semantics: Lock-free write access. Never, ever database dead-locks.
- gaius 13y agoBack in the 90s, Sybase Replication Server was pretty sweet, and we ran topologies you wouldn't believe...
- tony_landis 13y agoHere is the reference for update handlers for anyone wanting to check it out: http://docs.couchdb.org/en/latest/ddocs.html#update-functions http://docs.couchdb.org/en/latest/ddocs.html#update-function... It still requires writing code, and moving it into the database. Once that is done, how do you call that function against an arbitrary list of documents and pass the new values to it without writing even more code somewhere? This workflow of putting code/logic in the db is that it is forcing developers out of their preferred development environment, workflow, and most likely language. Not to mention the fact that debugging all these couchdb functions and map/reduce calls becomes a nightmare. And testing - not sure how that could be done efficiently. All of this this slows development. It is possible to implement some web apps completely in static html, js, and couchdb, eliminating the need for anything server side. In those cases, couchdb is one of a kind.