Mongodb collection object caching in Node.js

Question

I'm trying to implement a RESTful(ish) interface to a MongoDB database in Node.js. According to the docs, the the basic idiom is something like:

var mongo = require('mongodb'),
  Server = mongo.Server,
  Db = mongo.Db;

var server = new Server('localhost', 27017, {auto_reconnect: true});
var db = new Db('exampleDb', server);

db.open(function(err, db) {
     if(!err) {
        db.collection('test', function(err, collection) {
            // do stuff with collection
        });
     }
});

So there are three objects (server, db, and collection) involved in a basic DB access. My question is which of these can/should be loaded at startup and cached somewhere to be reused for every http request, and which must/should be recreated per request. My assumption is that it is okay for the server and db objects to be long lived, but I'm less sure about the collection object.

No, sorry, just a mistake cutting and pasting from two different places. Fixed. — gaufqwi
– gaufqwi, Commented Sep 29, 2012 at 18:59

edef · Accepted Answer · 2012-09-30 09:13:19Z

1

Save all three things (server connection, database and collection) and kick off your app. ODMs for MongoDB like Mongoose do themselves, in case you're doubtful. You might want to use async to avoid nesting your code too deeply.

Personally, I use mongo-lite which lets me do var db = require('mongo-lite').connect('mongodb://localhost/exampleDb', ['test']); After which I can fiddle with db.test, my collection. This saves me a lot of boilerplate.

edited Sep 30, 2012 at 9:13

answered Sep 30, 2012 at 9:06

edef

7524 silver badges13 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Sebastian Schürmann · Accepted Answer · 2012-09-29 13:19:08Z

0

The collection can be long-lived, especially when the server is not operating if a big numer of collections like this. It's just memory you are using.

answered Sep 29, 2012 at 13:19

Sebastian Schürmann

6096 silver badges19 bronze badges

Comments

supernova · Accepted Answer · 2012-09-29 14:32:03Z

0

why shouldn't it be? the collection object itself doesn't consume much memory, it provides all functions to interact with mongodb, query, save and so on. recreating it on every request and removing it afterwards makes no sense.

answered Sep 29, 2012 at 14:32

supernova

3,9033 gold badges25 silver badges37 bronze badges

Comments

Scott · Accepted Answer · 2012-09-30 02:07:30Z

0

Generally the callback from open should kick off the logic to start the rest of your application/server. Then you just hold on to that db reference and call db.collection per request. I usually have a service I can can call to get db ref from my REST resources to keep everything clean. Again this can vary depending on db/collection usage within the application.

answered Sep 30, 2012 at 2:07

Scott

1,0107 silver badges14 bronze badges

Collectives™ on Stack Overflow

Mongodb collection object caching in Node.js

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related