Linked by MOS6510 on Fri 2nd Aug 2013 18:06 UTC
Let’s say you’ve decided to set up a website or an application. You'll obviously need something to manage the data. Yes, that's right, a database. So, what is it going to be? MySQL, MS-SQL, Oracle or PostgreSQL? After all, nothing can be as amazing as a good old RDBMS that employs SQL to manage the data.

Well, allow me to introduce to you an entirely unique and unconventional Database model - NoSQL.

Thread beginning with comment 568758
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by Kroc
by henderson101 on Fri 2nd Aug 2013 22:57 UTC in reply to "Comment by Kroc"
Member since:

I've done it as a traditional database, a key/value store and an ORM, where I really didn't care what the DB looked like. Honestly, the best approach is to either ORM the dataset (I used Entity Framework code first in a number of projects, doing so, the database structure became competely opaque) or use tables for static data and K/V for dynamic data. The biggest issue with K/V is reporting on the data. If a reporting solution is critical (e.g. Sales, stats etc) then K/V really falls down. Pivoting giant chunks of data is no real fun. Neither is field bloat in traditional tabular databases, so the happy middle ground works well.

Reply Parent Score: 3