InfoQ Homepage Presentations CouchDB From 10,000 Feet
CouchDB From 10,000 Feet
55:15
Summary
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.
Bio
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.
About the conference
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.
Aug 14, 2009
-
Related Sponsored Content
-
Related Sponsor
/filters:no_upscale()/sponsorship/topic/2c0d72d2-1768-47c2-8f5b-24f3ef0ae0e0/QconNYrsb-1679560094156.png)
Community comments
Generic DB Schema
by Steve Tirtha,
Re: Generic DB Schema
by Jan Lehnardt,
2nd part
by Alexander Rodriguez,
2nd part
by Richard Paul,
Nice
by Dragan Sahpaski,
Re: Nice
by Jan Lehnardt,
Generic DB Schema
by Steve Tirtha,
Your message is awaiting moderation. Thank you for participating in the discussion.
Hi Jan,
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,
Steve
2nd part
by Richard Paul,
Your message is awaiting moderation. Thank you for participating in the discussion.
Very interesting talk, is part II doing going to be posted? Jan said a lot of the answers to questions asked were in the 2nd part.
Nice
by Dragan Sahpaski,
Your message is awaiting moderation. Thank you for participating in the discussion.
Nice presentation.
Although you are not a very good speaker.
Re: Nice
by Jan Lehnardt,
Your message is awaiting moderation. Thank you for participating in the discussion.
Dragan, oh boo! I'm not a native speaker and this was a very prestigious crowd. Can you point to any specific shortcomings? :) Thanks for the feedback anyway.
Re: Generic DB Schema
by Jan Lehnardt,
Your message is awaiting moderation. Thank you for participating in the discussion.
@Steve, CouchDB doesn't make schema migrations go away, it just lets you do be lazy with them as you don't have to do them upfront. CouchDB views and show functions (not mentioned as they weren't invented then) can morph you docs into anything you need.
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!
2nd part
by Alexander Rodriguez,
Your message is awaiting moderation. Thank you for participating in the discussion.
Nice presentation. Are you going to post the second part?