StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4574109
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2011-01-01T12:54:58.573
FavoriteCount
0
LastActivityDate
2011-01-01T12:54:58.573
LastEditDate
LastEditorUserId
0
OwnerUserId
130167
ParentId
4561950
PostTypeId
2
Score
16
ViewCount
0
LastEditorDisplayName
text
Body
Persisting sessions in the database limits your scalability. If scalability is not that important for you this (db + memcached) is a valid approach. One thing you need to keep in mind when using nonsticky-sesions are concurrent requests: when you have e.g. ajax-requests (executed in parallel/concurrently) they will be served by different tomcats (due to non-stickyness) and therefore access the session concurrently. As long as you have concurrent requests that might modify the session you need to implement some kind of synchronization / session locking. Perhaps this is of interest for you: I created the <a href="http://code.google.com/p/memcached-session-manager">memcached-session-manager</a> with the goal of both optimal performance and unlimited scalability. It can work with any memcached-compatible backend (e.g. also memcachedb, membase etc. or just memcached). Although it was originally created for a sticky-sessions approach, there's already a <a href="https://github.com/magro/memcached-session-manager/tree/nonsticky-sessions">branch for nonsticky-sessions</a> existing and a <a href="https://github.com/magro/msm-sample-webapp/tree/nonsticky-sessions">sample app</a> showing how/that it works. Right now there's a <a href="http://groups.google.com/group/memcached-session-manager/browse_frm/thread/b0106aa0a3eb3db0">thread on the mailing list on further improvements for nonsticky-sessions</a> (handling of concurrent requests and preventing single-point-of-failure).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POShare Sessions between tomcat instances (without using Sticky Sessions)
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMartinGrotzke
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
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COI just want to drop a note here that I just release memcached-session-manager with non-sticky sessions support (and support for tomcat7). The announcement with some details regarding non-sticky sessions: http://groups.google.com/group/memcached-session-manager/t/612891b0ae10649d
 singulars
 PostPostId
 PO
 UserUserId
 USMartinGrotzke

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.