Hm, flat files will rule the world? No more messy SQL, just iterate over the file's entries with a for loop - even Java programmers can understand that.
Sorry, but I am not convinced yet.
Sorry, but I am not convinced yet.
Edit: OK, read the CouchDB introduction now. Did not know that the "views" are server side. I have a past as a Java developer, and I have actually come across the "select all, then compute in Java" pattern several times in the real world.
If, however, you make a (willfully) ignorant assertion, people jump at the chance to tell you just how wrong you are.
Not that I want to advocate this approach, but I understand why someone would use it if, in the end, it generates more useful information.
(I think this was discussed elsewhere on HN, with "troll, don't inquire" as a disappointingly effective means of getting information.)
How terse the code is? How easy the code is to read? How likely the code is to be correct? How flexible the data model is to new requirements? How simply you can reason about what the code does?
Reasoning about what the code does is simple once you shift your paradigm to document from relational.
The only advantage of disk-backed hash table is ease of scalability, this is why they're useful for hm.... top 0.005% of web sites, who handle thousands of updates per second.