StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2750821
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2010-05-01T17:07:28.590
FavoriteCount
0
LastActivityDate
2010-05-01T17:07:28.590
LastEditDate
LastEditorUserId
0
OwnerUserId
228221
ParentId
2748825
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
I found a good answer in the comments in this link: <a href="http://blog.boxedice.com/2010/02/28/notes-from-a-production-mongodb-deployment/" rel="noreferrer">http://blog.boxedice.com/2010/02/28/notes-from-a-production-mongodb-deployment/</a> Basically option #2 seems to be the best way to go. Quote from David Mytton's comment: <blockquote> We decided not to have a database per customer because of the way MongoDB allocates its data files. Each database uses it’s own set of files: <blockquote> The first file for a database is dbname.0, then dbname.1, etc. dbname.0 will be 64MB, dbname.1 128MB, etc., up to 2GB. Once the files reach 2GB in size, each successive file is also 2GB. Thus if the last datafile present is say, 1GB, that file might be 90% empty if it was recently reached. </blockquote> from the manual. As users sign up to the trial and give things a go, we’d get more and more databases that were at least 2GB in size, even if the whole of the data file wasn’t use. We found this used a massive amount of disk space compared to having several databases for all customers where the disk space can be used to maximum efficiency. Sharding will be on a per collection basis as standard which presents a problem where the collection never reaches the minimum size to start sharding, as is the case for quite a few of ours (e.g. collections just storing user login details). However, we have requested that this will also be able to be done on a per database level. See <a href="http://jira.mongodb.org/browse/SHARDING-41" rel="noreferrer">http://jira.mongodb.org/browse/SHARDING-41</a> There are no performance tradeoffs using lots of collections. See <a href="http://www.mongodb.org/display/DOCS/Using+a+Large+Number+of+Collections" rel="noreferrer">http://www.mongodb.org/display/DOCS/Using+a+Large+Number+of+Collections</a> </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat is the recommended approach towards multi-tenant databases in MongoDB?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBraintapper
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. 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.