Re:Dear NoSQL: "SQL-isn't-scalable" is a lie
by barrkel on Tuesday March 02, 2010 @09:10PM
(#1163140)
Consistency, Availability, Partition tolerance. NoSQL stores usually sacrifice consistency, and instead settle for eventual consistency. SQL (i.e. RDBMS) stores, with their usual emphasis on transactions, must necessarily sacrifice something else. SQL that doesn't hew to a hard line on consistency and transactions doesn't really have all the features of SQL. This is the distinction that matters most, IMHO, in the NoSQL strand of thinking.
[ Parent
| on HN ]
I admit that the SQL vendors (besides MySQL) made a mistake by putting ACID above scalability; that's clearly not always the right choice. However, CAP still allows a SQL database that is scalable, consistent, and available.
Re:Dear NoSQL: "SQL-isn't-scalable" is a lie
by pashields on Tuesday March 02, 2010 @10:14PM
(#1163261)
No, that's exactly what CAP doesn't allow. Unless by scalable you mean non-horizontal scaling. In which case yes, but we already knew that big machines make things fast.
Re:Dear NoSQL: "SQL-isn't-scalable" is a lie
by evgen on Wednesday March 03, 2010 @12:22AM
(#1163475)
> CAP still allows a SQL database that is scalable, consistent, and available
Name one please. It seems you are either fundamentally mistaken about what CAP implies or are constraining the "solution" to a clustered system that is effectively a single RDBMS hiding behind lots of tightly-coupled components.
A tightly-coupled (whatever that means) cluster sounds like a perfectly legitimate way to scale to me.