Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
0Activity
0 of .
Results for:
No results containing your search query
P. 1
mongodb

mongodb

Ratings: (0)|Views: 58|Likes:
Published by sanaz.m5349

More info:

Published by: sanaz.m5349 on Aug 04, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

08/04/2011

pdf

text

original

 
About This Book
License
The Little MongoDB Book book is licensed under the Attribution-NonCommercial 3.0 Unportedlicense.
You should not have paid for this book.
You are basically free to copy, distribute, modify or display the book. However, I ask that youalways attribute the book to me, Karl Seguin and do not use it for commercial purposes.You can see the full text of the license at:
http://creativecommons.org/licenses/by-nc/3.0/legalcode
About The Author
Karl Seguin is a developer with experience across various fields and technologies. He's anexpert .NET and Ruby developer. He's a semi-active contributor to OSS projects, a technicalwriter and an occasional speaker. With respect to MongoDB, he was a core contributor to theC# MongoDB library NoRM, wrote the interactive tutorialmonglyas well as theMongo Web Admin. His free service for casual game developers,mogade.com, is powered by MongoDB. His blog can be found at
http://openmymind.net
, and he tweets via@karlseguin
With Thanks To
A special thanks toPerry Nealfor lending me his eyes, mind and passion. You provided mewith invaluable help. Thank you.
Latest Version
The latest source of this book is available at:
http://github.com/karlseguin/the-little-mongodb-book
.2
 
Introduction
It's not my fault the chapters are short, MongoDB is just easy to learn.It is often said that technology moves at a blazing pace. It's true that there is an ever grow-ing list of new technologies and techniques being released. However, I've long been of theopinion that the fundamental technologies used by programmers move at a rather slow pace.One could spend years learning little yet remain relevant. What is striking though is the speedat which established technologies get replaced. Seemingly over-night, long established tech-nologies find themselves threatened by shifts in developer focus.Nothing could be more representative of this sudden shift than the progress of NoSQL tech-nologies against well-established relational databases. It almost seems like one day the webwas being driven by a few RDBMS' and the next, five or so NoSQL solutions had establishedthemselves as worthy solutions.Even though these transitions seem to happen overnight, the reality is that they can takeyears to become accepted practice. The initial enthusiasm is driven by a relatively small setof developers and companies. Solutions are refined, lessons learned and seeing that a newtechnology is here to stay, others slowly try it for themselves. Again, this is particularly truein the case of NoSQL where many solutions aren't replacements for more traditional storagesolutions, but rather address a specific need in addition to what one might get from traditionalofferings.Having said all of that, the first thing we ought to do is explain what is meant by NoSQL. It'sa broad term that means different things to different people. Personally, I use it very broadlyto mean a system that plays a part in the storage of data. Put another way, NoSQL (again,for me), is the belief that your persistence layer isn't necessarily the responsibility of a singlesystem. Where relational database vendors have historically tried to position their software asa one-size-fits-all solution, NoSQL leans towards smaller units of responsibility where the besttool for a given job can be leveraged. So, your NoSQL stack might still leverage a relationaldatabases, say MySQL, but it'll also contain Redis as a persistence lookup for specific parts of the system as well as Hadoop for your intensive data processing. Put simply, NoSQL is aboutbeing open and aware of alternative, existing and additional patterns and tools for managingyour data.You might be wondering where MongoDB fits into all of this. As a document-oriented database,Mongo is a more generalized NoSQL solution. It should be viewed as an alternative to relationaldatabases. Like relational databases, it too can benefit from being paired with some of themore specialized NoSQL solutions. MongoDB has advantages and drawbacks, which we'll coverin later parts of this book.As you may have noticed, we use the terms MongoDB and Mongo interchangeably.3

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->