Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 10 years ago.

I ve been reading up on a lot of posts about non-relational databases, the whole NOSQL movement, and there s a lot of fresh new activity around it. It seems like a very interesting approach to building highly scalable web applications but unfortunately (but also a good thing at this nascent stage) there isn t quite a clear leader/standard at the moment.

My background is in the LAMP stack (with MySQL as the dB) and I wanted to understand what differences and limitations there would be - but with using the example of real life web applications out there. There s a ton of good articles about the theory of pros/cons of RDBMS vs non-RDBMS, but I haven t found anything that walks through an example of how an existing web app (for example social bookmarking) would be built different to take advantage of the new dB structure and what features one would have to leave out if any - where the NOSQL dB could be key-value or document-centric or graphs.

Would anyone be willing to take a stab at a high-level comparison of a NOSQL vs RDBMS model/architecture of a real-world web app (such as social bookmarking or any other example that might explain the concepts well)?

For reference to others, here are a few of the articles I have come across:

Answer 1

The main reason is scale (Facebook, MySpace)

Check out these articles:

Facebook s Cassandra - A Massive Distributed Store

MySpace Qizmt - MySpace s Mapreduce Framework

As you are already using Lucene, this may be of interest:

Katta - Lucene in the cloud

友情链接