The thrill of a new technology: CouchDB
1–10 of 48 posts
Re: The thrill of a new technology: CouchDB
#2I work only with relational db...but this is a great tech!
Re: The thrill of a new technology: CouchDB
#3Hm, 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.
Re: The thrill of a new technology: CouchDB
#4Hm, 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.
Tichy, give it a spin. The ease of execution (and the sheer speed, even over giant amounts of data) is impressive.
Re: The thrill of a new technology: CouchDB
#5Hm, 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.
Tichy, give it a spin. The ease of execution (and the sheer speed, even over giant amounts of data) is impressive.
What do you mean by impressive "ease of execution"?
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?
Re: The thrill of a new technology: CouchDB
#6A document based DB is not like a flat file. They do index for fast retrieval.
It is just that the indexes are added based on what queries are made. You can be explicit about what indexes you want maintaned, but it is often good-enough to just perform a query and have the db figure out how to index to make that query faster.
It's pretty much dynamic-typing vs static-typing for databases (plus the document-entries instead of row-column-entries).
Re: The thrill of a new technology: CouchDB
#7Earlier quoted context omitted.
Tichy, give it a spin. The ease of execution (and the sheer speed, even over giant amounts of data) is impressive.
What do you mean by impressive "ease of execution"? 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?
The code is easy to read, and the data model is as flexible as you want it to be, since it's schemaless.
Reasoning about what the code does is simple once you shift your paradigm to document from relational.
Re: The thrill of a new technology: CouchDB
#8Earlier quoted context omitted.
What do you mean by impressive "ease of execution"? 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?
The code is easy to read, and the data model is as flexible as you want it to be, since it's schemaless. Reasoning about what the code does is simple once you shift your paradigm to document from relational.
Do your research. "document-based" DBs already "ruled the world" right until relational databases were invented, which quickly obsoleted them.
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.
Re: The thrill of a new technology: CouchDB
#9No, graph databases will rule the world. Couch only supports trees, which is annoying if you want to have relationships between "documents".
Also, Couch's implementation of map/reduce arbitrarily limits the kinds of queries you can run.
If you actually want to ditch your relational database, take a look at things like KiokuDB, Elephant, AllegroCache, and so on. They may not have exciting web 2.0 screencasts, but the technology is much better. (I am biased towards KiokuDB, since I helped write it, but it has been very easy to use KiokuDB instead of a relational database; there has been significantly less code in our apps, tests have been much easier to write, and I don't think we've lost any runtime speed either. I really need to write a long blog post about this, but I haven't had time.)
It is good that the world is gradually working their way up to object/graph databases, though. Last week it was "OMG KEY VALUE STORES SOLVE EVERY PROBLEM", this week it is "DOCUMENT DATABASES WILL RULE THE WORLD", so hopefully the blogosphere is only a few weeks away from enlightenment ;)
Re: The thrill of a new technology: CouchDB
#10Hm, 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.
Tichy, give it a spin. The ease of execution (and the sheer speed, even over giant amounts of data) is impressive.
I simply don't believe that this model scales "over giant amounts of data", at least in any sort of real-world usage scenario. Can you back up this claim with benchmarks?