I love learning in the open. The simple process of relaying what you see/do/think/learn/fear/love can, itself, be illuminating. So here we go again - I'm going to fuddle around live, with some edge technologies, and you get to laugh at me.
I've received a flood of emails since we launched the revamped Tekpub site (using Rails and MongoDb) a few months back. Many people have been surpised to find out that we use both MongoDb *and* MySQL. Here's the story of how we did it and why.
Lately I’ve been working with Mongo, creating a C# driver with Karl Seguin and Andrew Theken (and James Avery and Jason Alexander) and today I checked in some optimizations that made me really stoked and I thought I would share. In short – I think we have a roundly working (but young) Linq provider for MongoDB.
In my last post I took a look at possible approaches to using NoSQL and Reporting, and many people wanted to see what this might look like in practice. In part one, below, I’ll show you ways to work with a NoSQL solution (in this case DB4O) in ways that you will find pretty familiar. I’ll also show you the freedom you can have as a developer when you stop thinking relationally.
I’m a big fan of giving relational systems the boot when it comes to persisting application data. The more I work with document (or OO) databases, the more I feel really, really dumb for doing it any other way. One question that comes up a lot in conversation, however, is “dude what about reporting – you can’t do that with NoSQL very well now can ya?” and the answer is “yes, correct. You can’t”. As with all things programming: right tool for the right job.
