[Lazamataz]

However, a NoSQL database

Yes, my former boss David C. mentioned this as well. There are pros and cons to this approach as well. One major one, to my mind, is there is no ACID for NoSQL (atomicity, consistency, isolation, durability). There's also little standardization in API's or Query Languages for NoSQL. Therefore, I conclude that it is an immature -- albiet promising -- technology.

SQL doesn't necessarily scale, but there are methods of writing code so that it scales a lot better:

1. Connecting when request required, dropping connection immediately. Seems counterintuitive, but it works.
2. No Dynamic SQL *EVER*!!!!

   On the SQL side itself:

3. Watching carefully the number of indexes. Inserts slow down a lot for indexes.
4. Watching cartesians!!!
5. Good PK selection, low use of FK.
6. Use of Profiler to see where most of your time is spent.

[justlurking]

One major one, to my mind, is there is no ACID for NoSQL (atomicity, consistency, isolation, durability).

FR doesn't need ACID. It's a news aggregation site, with user comments. If it loses a comment, or posts a couple of simultaneously posted ones out of order, it's no big deal.

There's also little standardization in API's or Query Languages for NoSQL.

Once you settle on a database and API, you stick with it. There's no need to make it portable to other databases.