Ask HN: It's 2012, what database solution do you now pick for a Web 2.0 site?
Congratulations, it's now the year 2012. Your ready to start a brand new Web 2.0 Website. Now all you need to do is pick a persistent storage (aka a database). Which one do you pick now?
You can choose the traditional paid SQL Server, Oracle or maybe the traditional unpaid MySQL. Older ones came up to replace it such as PostGresql. Then comes the nontraditional such as Cassandra, HBase, MongoDB, and so forth. With all these choices, which one does one now pick? How about if your not 100% sure how your site will scale in the future?
It's a startup, the idea will change as time goes on.
(
17 comments
| 5 points
| on HN
)
From what I've seen, most start out with a RDBMS and switch to hybrid RDBMS/OODB later on. I've also seen some switch entirely to OODB from RDBMS and back into a hybrid.
There's also a case for schemaless document oriented databases like MongoDB. Honestly, I haven't seen 'serious' uses of document oriented databases other than for distributed caching.
In general, 'big' data needs structure.
One of days it might even become common to see most browsers support indexeddb (sql like) and local storage (kvp like).
So back to my point; efficiency, compatibility and familiarity is key for rapid application development, which is a must have for start-ups.
If you are going to bring in off shore guys/gals it will be hard to find them proficient in some of the newer dbs. So the learning curve and cost inefficiencies maybe create a lost of momentum (time) for you. If I were to build my framework from scratch I would probably still use MySQL for certain thing but definitely move to a NoSQL (mongodb/dynamodb).
As for old, doesn't PostgreSQL have roots dating all the way back to 1982?
Early optimization is the root of all evil.
There isn't a one size fits all solution.