Personally, PostgreSQL all the way, on your own hardware. We have
benchmarked our postgreSQL instances to over 100k queries per second, and
they aren't even on SSD (although this assumes the dataset fits in memory).
And it's way more proven than MongoDB.
On Thu, Sep 27, 2012 at 6:43 PM, Jason
I would say it depends. If the content you are planning to store is very
varied in shape (number of fields, structure) mongodb is is a very suitable
candidate (shutterfly uses it to store all the metadata for uploaded photos
which varies a lot depending on the camera that took the photo). If on
I'm building a node.js project that will grow to a large authentication
data group (hopefully), and I'd like to make the right decision now.
My options are:
-- PostgreSQL sharding, like Instagram does
-- MongoDB
-- Something more creative
I'll likely use some kind of VM solution like
