snydeq writes: "Andrew Glover provides an in-depth look at MongoDB, one of several NoSQL data stores filling the voids left by traditional relational DBs. 'Working with MongoDB is not without challenges. For starters, Mongo requires a lot of memory, preferring to put as much data as possible into working memory for fast access. In fact, data isn't immediately written to disk upon an insert (although you can optionally require this via a flag) — a background process eventually writes unsaved data to disk. This makes writes extremely fast, but corresponding reads can occasionally be inconsistent. As a result, running Mongo in a nonreplicated environment courts the possibility of data loss,' Glover writes. 'The relational database is still the staple data store for the vast majority of applications built today. But for some applications, the flexibility offered by Mongo provides advantages with respect to development speed and overall application performance.'"
Top Ten Things Overheard At The ANSI C Draft Committee Meetings:
(8) I'm on the committee and I *still* don't know what the hell
#pragma is for.