You can do it with MySql, or with files in append mode with "message_id - message", and everything else.
I think that KV stores are great, but if you create a false sense of coolness this is going to hurt in the long run. It is important to show people why really new forms of DBs can be useful and important.
edit: If the point is instead the fact that the DB talks directly HTTP, the w.ebchat.com chat PHP layer is ridiculous, just a wrapper that takes parameters from the HTTP side and run a query returning back the data. I can only see the HTTP protocol as interface to KV DB as a good way to lost a lot of performances without a reason.
@antirez the thing is that CouchDB is designed for replication. Every CouchApp is a p2p web app. This is different from the web we've known before.
CouchDB will never be as fast as some other k/v stores, but http based peer replication gives us a robust offline mode (and portable api) so that applications can run at the Edge.
the scripting layer has very little concern in the traditional web model, there are clear advantages to having that work done in the browser, hence the popularity of things like ajax and jquery.
why is creating any trivial website backed by a cms that isnt cuttie cooker blogger template still the domain of the ruby / phpist, we have had plenty of time to solve these problems with the traditional browser > php/ruby > mysql model, time for someone to come along with something new.
Yes, it is good thing. But will that method perfect for every use case.
Think about maintaining DB(Mysql, Sql language), Web server(Crazy config files), application server (Ruby or PHP), Client side(Javascript) just for personal blog/site.
Here layers are less and Languages(only one) and config files are less.
EDIT: "And less is good" , Arguments are endless unless you are talking about specific use case.
http://w.ebchat.com/channel/hackernews
You can do it with MySql, or with files in append mode with "message_id - message", and everything else.
I think that KV stores are great, but if you create a false sense of coolness this is going to hurt in the long run. It is important to show people why really new forms of DBs can be useful and important.
edit: If the point is instead the fact that the DB talks directly HTTP, the w.ebchat.com chat PHP layer is ridiculous, just a wrapper that takes parameters from the HTTP side and run a query returning back the data. I can only see the HTTP protocol as interface to KV DB as a good way to lost a lot of performances without a reason.