StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6419007
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-06-21T00:14:37.350
FavoriteCount
0
LastActivityDate
2011-06-21T00:14:37.350
LastEditDate
2017-05-23T10:08:08.987
LastEditorUserId
-1
OwnerUserId
11926
ParentId
6404646
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> Can I use Redis as a queue but is not the best way to save information, maybe MongoDB is? </blockquote> You can(should) use Redis as your queue. It is going to be extremely fast. I also think it is going to be very good option to save the information inside Redis. Unfortunately Redis does not do any timing(yet). I think you could/should use <a href="https://stackoverflow.com/questions/4762016/node-js-workers-background-processes/4782762#4782762">Beanstalkd</a> to put messages on the queue that get delivered when needed(every x seconds). I also think cron is not that a very good idea because you would be needing a lot of them and when using a queue you could do your work faster(share load among multiple processes) also. Also I don't think you need that much memory to save everything in memory(makes site fast) because dataset is going to be relative simple. Even if you aren't able(smart to get more memory if you ask me) to fit entire dataset in memory you can rely on <a href="http://redis.io/topics/virtual-memory" rel="nofollow noreferrer">Redis's virtual memory</a>. <blockquote> It seems pretty simple but needing to have more than 1 server to guarantee the server is down and make everything work together is not so easy. </blockquote> Sharding/replication is what I think you should read into to solve this problem(hard). Luckily Redis supports replication(sharding can also be achieved). MongoDB supports sharding/replication out of the box. To be honest I don't think you need sharding yet and your dataset is rather simple so Redis is going to be faster: <ul> <li><a href="http://redis.io/topics/replication" rel="nofollow noreferrer">http://redis.io/topics/replication</a></li> <li><a href="http://www.mongodb.org/display/DOCS/Sharding+Introduction" rel="nofollow noreferrer">http://www.mongodb.org/display/DOCS/Sharding+Introduction</a></li> <li><a href="http://www.mongodb.org/display/DOCS/Replication" rel="nofollow noreferrer">http://www.mongodb.org/display/DOCS/Replication</a></li> <li><a href="http://ngchi.wordpress.com/2010/08/23/towards-auto-sharding-in-your-node-js-app/" rel="nofollow noreferrer">http://ngchi.wordpress.com/2010/08/23/towards-auto-sharding-in-your-node-js-app/</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POArchitecture to create an uptime monitor in Node.js
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USAlfred
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. This table or related slice is empty.
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.