Clarifications to My CouchDB PostPosted: February 6, 2009
I got great feedback on my previous post about CouchDB, and I wanted to clarify a few points.
Regarding mattly’s point, I really should have said “most of this is going to be obsolete”, not all. He gives several examples where a middleware tier is necessary because CouchDB doesn’t have a system in place to deal with certain tasks (like comment spam detection). However, my understanding is that CouchDB’s upcoming security model really is supposed to replace the middleware tier. What prompts me to say this is the focus on “CouchApps”, which would run on the user’s computer (CouchDB and all), and synchronize the database with a master (“Eventual Consistency”) when the client was finished. In essence, it’s a way to cache the database on each client. Security/validation then becomes a matter of which client databases are allowed to update the master. As far as I understand, it’s very similar to the git source control security model. More here.
Anyway, thanks for the feedback, and I look forward to talking more about CouchDB in the future!