This presentation takes a look at CouchDB from 10,000 ft. CouchDB is a document oriented database with a highly acclaimed REST API and replication support, that solves problems of high-traffic, distributed peer-to-peer, and offline applications. all at the same time. You will learn to decide when CouchDB is a good fit for your project and when you are better off with a traditional database.
Jan Lehnardt is an Open Source software consultant specialising in internet technologies. Jan is the co-founder of Freisatz, a company bringing typographic bliss to everyone and a contributor to the CouchDB project. He has a keen eye for user experience and typography.
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community. QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
Generic DB Schema
nice presentation. However, I still don't get how CouchDB overcomes the issue with generic DB Schema. You mentioned in the minutes 11.45, that it is not good in performance, because of the JOINS. But the reason to have a generic DB Schema is because the developer want to make the application flexible. So everytime there is a new function needed, he does not need to create a new DB or a new class. Do you have answer for this?
Gruß aus Heidelberg,
Re: Generic DB Schema
It is a trade-off question, if you can afford a 9-table JOIN and live with the performance implications, that's fine. Large websites do run without a single JOIN because they can't.
In addition, not all data is inherently relational. Being able to store things flexibly makes for more natural data handling, less code, less bugs, less headache.
Thanks for your question!