News for hackers. Stuff that matters.
Re:'Slacker DB' shootout: SimpleDB vs. CouchDB vs. App Engin... by anuraggoel on Tuesday March 24, 2009 @01:25PM (#530426)
"Now that disk space is so cheap and many of the data models don't benefit as much from normalization, JOINs are easy to leave behind."

JOINs and data normalization were not created to get around disk space constraints.

http://en.wikipedia.org/wiki/Database_normalization#Objectiv...

For the average web application not running on app-engine like infrastructure, I believe the following order of questions would be more prudent:

   1. Do I need a database?
   2. Can I work with a relational database? SQLite? PostgreSQL/MySQL?
   3. Now, do I really need the new hotness?
And if you do need the new hotness, may I also suggest Tokyo Cabinet? I am afraid I can't rate its 'value' on a scale of 10, but I'd say it's pretty high for a free product.
Re:'Slacker DB' shootout: SimpleDB vs. CouchDB vs. App Engin... by cnu on Wednesday March 25, 2009 @02:12AM (#531524)
I have been trying out Redis (http://code.google.com/p/redis/) which is also quite good.
Re:'Slacker DB' shootout: SimpleDB vs. CouchDB vs. App Engin... by lsb on Tuesday March 24, 2009 @05:07PM (#530839)
It seems like for 1, if you just have a bunch of files somewhere, you should be able to keep that in source control. When is it a good idea (if ever) to keep a SQLite database in git?