When I first got started with MongoDB in my ASP.NET development I wasn’t able to find as much information as I hoped to on how to get started with MongoDB. All of the core documentation focuses on interacting with the driver and doesn’t give a high-level overview of how to use the driver in an actual project. After getting several projects up and running on MongoDB, I wanted to take a break and provide this much needed guide.
Leave it to O’Rielly to give a great summary of NoSQL—and express what I have been telling other developers. NoSQL is not a technology. It’s a different way of looking at large data sets and data-driven applications. I have been busy adding NoSQL to my developer’s utility belt lately by introducing MongoDB into the projects that I am building. I have already referenced my BrainDonor.Mongo project in some of my other posts. I like to think of it as my formal announcement that I am a card-carrying member of the NoSQL movement. For me, the movement is about not putting all my data eggs in one basket. When it comes to development languages and platforms, I am a true polyglot programmer—and I must extend that further into data.
A common component of many of the websites that I build are small administrative areas where clients are able to perform tasks such as downloading leads or scheduling appointments. Until recently, most of those websites were built to run on top of a content management framework–with the CMS providing most of the back-end interface that I deliver. I started using Twitter’s Bootstrap framework to deliver a consisten look and feel with our ASP.NET MVC3 applications. Bootstrap provided me with a clean CSS grid system, clean controls, and a host of other components. The biggest disconnect between Bootstrap and MVC3 is the unobtrusive validation.