The CouchDB project has been getting a lot of talk lately, all over the blogosphere and in particular in Python circles, who like JSON and REST and are excited at the new move to them from XML. I really liked what I saw. I also knew I could have liked it a lot more.
You know something interesting is happening when someone with my anti-XML track record says the following: XML should not have been dropped from CouchDB.
I can clarify and reaffirm that I am not crazy by saying that this does not mean JSON should not have been added, but that it should not have replaced anything. In other words, both are fine. While we're at it, why does it matter what format the "document" is in? Be it an XML document, a JSON serialization, or a photo, anything could benefit from the basic architecture of CouchDB.
Looking into the details, I'm disappointed that the distribution model is just smarter replication. Something like this really should be able to do sharding out of the box, with its really unique identifiers and revisioned nature.
Can CouchDB satisfy my requriements or do I need to write SofaCouchDB?
I write here about programming, how to program better, things I think are neat and are related to programming. I might write other things at my personal website.
- ► 2014 (52)
- ► 2012 (19)
- ► 2011 (19)
- ► 2010 (32)
- ► 2008 (28)
- How To Stop Me From Buying An iPod Touch
- How to Confuse _ and locals()["_"]
- How to Pretend Zope Doesn't Exist
- How to Add Memory Leaks to Python
- Python, Concurrency, and My Two Cents Today
- How to Shop for a Portable Device
- How to Exploit All of You For Traffic
- How to Improve on CouchDB
- Charlotte Python Group: First Meeting
- Brain Dump 20070904
- ▼ September (10)