Mongo vs minimongo

When we define a collection, we want both the server and client to know about it so we do it in the 'both' folder. This means the collection will essentially exist in two places - on the server it will communicate with Mongo and on the client it will communicate with Minimongo.

$You can get different results depending on server vs client\label$

Now you might ask what is the difference between the data in Mongo and the data in Minimongo? For our current app the answer is nothing! Minimongo will mimic Mongo exactly until we remove the package autopublish from our application. autopublish simply 'publishes' all your data to the client and is added by default to help you get up and running (note that you can see your currently installed packages by opening the file .meteor/packages in your app).

Obviously we don't always want all our data in Minimongo as it could be a security hazard and also it could get very slow (imagine if you had 1000 teams). But let's just leave the autopublish training wheels there for a little longer.