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 568734
To read all comments associated with this story, please click here.
by Hiev on Fri 2nd Aug 2013 19:00 UTC
Member since:

NoSQL databases were a boom for a time till many started to note that it didn't solved much of the scalability issues, and it was just on pair with traditional SQL Databases.

Edited 2013-08-02 19:00 UTC

Reply Score: 4

RE: ...
by Lennie on Fri 2nd Aug 2013 22:09 in reply to "..."
Lennie Member since:

That totally depends on the needs of the application.

It's easier to scale something like Redis than to scale a SQL-server.

But that doesn't mean you need to rely on just one.

PostgreSQL has a key value store called hStore and newer version have a JSON-type and also Foreigh Data Wrappers that can talk to other SQL or NoSQL or flat files or webclients, DNS-clients, whatever you want to create code for.

Reply Parent Score: 3

RE[2]: ...
by Hiev on Fri 2nd Aug 2013 23:35 in reply to "RE: ..."
Hiev Member since:

It's easier to scale something like Redis than to scale a SQL-server.

That depends of you definition of scale.

Reply Parent Score: 3

RE: ...
by Soulbender on Sat 3rd Aug 2013 04:11 in reply to "..."
Soulbender Member since:

Eh, NoSQL and RDBMS's solve different problems and it's not only about scalability.
If your data is relational then an RDBMS is the best choice but for data that isn't relational (and a lot of data isn't) you might want to look at NoSQL. At least it might reduce the chance that you use an RDBMS as a glorified flat-file storage...

Reply Parent Score: 4