StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhat makes Cassandra (and NoSQL in general) a better solution to an RDBMS?
primarykey
Id
3673125
data
AcceptedAnswerId
0
AnswerCount
11
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2010-09-09T01:14:08.797
FavoriteCount
6
LastActivityDate
2017-02-24T01:13:54.557
LastEditDate
2017-02-24T01:13:54.557
LastEditorUserId
426332
OwnerUserId
442974
ParentId
0
PostTypeId
1
Score
17
ViewCount
14473
LastEditorDisplayName
text
Body
Well, NoSQL is a buzzword right now so I've been looking into it. I'm yet to get my head around ColumnFamilies and SuperColumns, etc... But I have been looking at how the data is mapped. After reading <a href="http://arin.me/blog/wtf-is-a-supercolumn-cassandra-data-model" rel="noreferrer">this</a> article, and others, it seems the data is mapped in a JSON like format. <pre><code>Users = { 1: { username: "dave", password: "blahblah", dateReged: "1/1/1" }, 2: { username: "etc", password: "blahblah", dateReged: "2/1/1", comment: "this guy has a comment and dave doesns't" }, } </code></pre> The RDBMS format would be: <pre><code>Table name: "Users" id | username | password | dateReged | comment ---+----------+----------+-----------+-------- 1 | dave | blahblah | 1/1/1 | ---+----------+----------+-----------+-------- 2 | etc | blahblah | 2/1/1 | this guy has a comment and dave doesn't </code></pre> Assuming I understand this correctly and my above examples are right, why would I choose the RDBMS design over the NoSQL design? Personally, I'd much rather work with the JSON structure... Does this mean I should choose NoSQL over, say, MySQL? I guess what I'm asking is "when should I choose NoSQL over RDBMS?" On a side note, as I've said, I'm still not fully understanding how to go about implementing a Cassandra database. Ie, how do I create the above Users table in a new database? Any tutorials, documentation, etc you could point to would be great. My google'ing hasn't turned up much in terms of 'starting from scratch'...
Tags
<sql><database><nosql><cassandra>
Title
What makes Cassandra (and NoSQL in general) a better solution to an RDBMS?
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USMehdi LAMRANI
UserOwnerUserId
1. USdave
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POWhat makes Cassandra (and NoSQL in general) a better solution to an RDBMS?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POWhat makes Cassandra (and NoSQL in general) a better solution to an RDBMS?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POWhat makes Cassandra (and NoSQL in general) a better solution to an RDBMS?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.