I think it's rather bold to say 'better' rather than just 'different.' It's unclear how a couchDB database would fare with perhaps 50 million items stored in it, or if couchDB would be at all suitable for answering queries such as 'how many salespeople reached their quotas during the last quarter.' Further, the 'benefit' of a schemaless database seems undesirable to any application where data integrity and transaction processing are important. There was a time that Microsoft Access was similarly touted as 'the best' because anyone and everyone could whip up a database with no experience. Many, if not most, of these were horrendous mishmashes of gobbledegook that performed badly and were nightmarish to maintain after awhile.
So while I have no direct experience with couchDB, I feel confident saying it is not absolutely better than mysql, but that it might be better in some situation(s) and much worse in others. On Jan 3, 4:04 pm, mobiledream...@gmail.com wrote: > http://pylab.blogspot.com/2009/01/ten-reasons-why-couchdb-is-better-t... > > Guys I wrote up a small list of reasons why i think couchdb is way bettter > than mysql. Do let me know what you think > > -- > Gpirate the top torrent search enginehttp://gpirate.com
