From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Carlos Mennens <carlos(dot)mennens(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: NoSQL -vs- SQL |
Date: | 2010-10-12 01:50:02 |
Message-ID: | AANLkTi=XLvp_FT40M5aiE6ZD4RvXs2xKXC2p2VeaxM14@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Oct 11, 2010 at 5:46 PM, Carlos Mennens
<carlos(dot)mennens(at)gmail(dot)com> wrote:
> Just wondering how you guys feel about NoSQL and I just wanted to
> share the following article...
>
> http://www.linuxjournal.com/article/10770
>
> Looking to read your feedback and / or opinions.
Here's my opinion. Key-value store is NOT NEW. Calling it a new name
(NoSQL) is kind of counter intuitive for me. I've used key-value
stores since I wrote my first program in 1985. For things like
session management they are great. The label NoSQL covers way to much
to mean any one thing. It's new speak for management. If a key value
store works use it. If a particular db /storage engine that happens
to not rely on sql does something well, then reference THAT db /
storage engine.
SQL database engine can be arbitrary enough that no one just says "we
use SQL", at least not in an engineering department.
memcached is a type of NoSQL db, and so are mongo, but they're
optimized for fundamentally different behavior and usage patterns.
When I talk about a particular SQL database, I name it. Seldom do I
ever talk about the aggregate group that is "SQL Databases." It's a
large and poorly defined set.
--
To understand recursion, one must first understand recursion.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter C. Lai | 2010-10-12 01:58:03 | Re: NoSQL -vs- SQL |
Previous Message | Dann Corbit | 2010-10-12 00:42:01 | Re: NoSQL -vs- SQL |