Do we need to have a client side moxi set up for java on Couchbase Server 2.0 ? if not ,then how do we maintain the database connection pool ?
- Thanks
Wed, 10/05/2011 - 09:48
ingenthr
Offline
Joined: 03/16/2010
Groups:
Assuming you're using the 2.8 developer preview linked off of the Couchbase server 2.0 page, no.
The Java client library is cluster aware, so it will automatically build connections to the correct nodes and manage them. No moxi is needed.
There is not a connection pool, as it has a non-blocking connection to each server and we manage the individual requests your calls to the client API will create. In fact, in the client we deduplicate requests for the same item/document for efficiency reasons. We've not usually seen a need for a connection pool except in extreme situations like data loading, and in that case it's easier to just give each loader it's own CouchbaseClient.
Assuming you're using the 2.8 developer preview linked off of the Couchbase server 2.0 page, no.
The Java client library is cluster aware, so it will automatically build connections to the correct nodes and manage them. No moxi is needed.
There is not a connection pool, as it has a non-blocking connection to each server and we manage the individual requests your calls to the client API will create. In fact, in the client we deduplicate requests for the same item/document for efficiency reasons. We've not usually seen a need for a connection pool except in extreme situations like data loading, and in that case it's easier to just give each loader it's own CouchbaseClient.