connection best pracrtices

[yaronn]

I use node-vertica in an express web app.

Is it better to open one connection per the whole app (e.g. mongo style)? Or open the connection whenever I need it (postgress style)?

[wvanbergen]

I wouldn't suggest to using one connection, because you can only run one query at the time per connection. This is bad if you want to use node's parallelism. Depending on your use case I would do one of the following:

• If your app mostly/only reads data from the database, use a connection pool. This library doesn't come with connection pooling, so you have to set that up yourself. This is pretty simple by using the generic-pool library.
• If your application does a lot of data loading, manage the connections yourself. Just open one when you need it and close it afterwards. Keep in mind that a transaction can only run within the scope of a connection, and cannot be shared between multiple connections.

[runk]

If you use the express framework, I think it's a good point in using build-in cluster module in node. So then you'll have N workers and each of them will do their own tasks and has its own connection. When one worker in the waiting state and working with vertica connection others can handle new requests and perform them independently.

[wvanbergen]

I updated the README to include some of this info and added some more documentation.