StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14461670
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-22T15:07:08.370
FavoriteCount
0
LastActivityDate
2013-01-22T15:07:08.370
LastEditDate
LastEditorUserId
0
OwnerUserId
1167429
ParentId
14459795
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
In my opinion, go with MySQL. The two biggest points you will think about when making the decision are: 1) Have you thought about your use-cases? You said you want to implement a follower system. If you're only going to be displaying a list of followers which each user has, then the Redis <code>SET</code> will be enough. But what if you want to get a list of "A list of users which you are currently following"? You can't dig that up easily from your Redis <code>SET</code>, right? Or how about if you wanted to know if User-X is following User-A ? If User-A had 10,000 followers, this wouldn't be easy either would it? MySQL is much more flexible when querying different types of results in different scenes. 2) Do you really need the performance difference? As you know, Redis IS faster than MySQL in these kinds of cases. It is a simple Key-Value system, so it will exceed the performance of MySQL. Checking out performance results like these: <a href="http://colinhowe.wordpress.com/2009/04/27/redis-vs-mysql/" rel="nofollow">http://colinhowe.wordpress.com/2009/04/27/redis-vs-mysql/</a> <a href="http://ruturaj.net/redis-memcached-tokyo-tyrant-and-mysql-comparision/" rel="nofollow">http://ruturaj.net/redis-memcached-tokyo-tyrant-and-mysql-comparision/</a> But the performance difference between Redis and MySQL really starts to kick in only after about 5,000request/sec . Otherwise you'd wouldn't be seeing a difference of more than 50ms. Performance difference will not be an issue until you have a VERY large traffic. So, after thinking about these two points, MySQL would be a better answer. Redis will be good only if: 1) The purpose of the set/list is specific, and there is no need for flexibility in the future 2) You feel that the performance difference will actually have an effect on your architecture.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFollower System, better in MySQL or Redis?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USashiina
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.