CouchbaseClusterHelper Initialize

I’m upgrading our .NET Web application to use Couchbase throughout, but, since we’re running multiple components, it seems like using the CouchbaseClusterHelper as a singleton would be great.

The issue I’m noticing, however, is that the Initialize() method that must be called before leveraging Couchbase will re-initialize if called subsequent times.

We’ve got multiple components that all would want to communicate to the same cluster, each without knowledge of the the others - and we’d want to leverage a common singleton inside the application, to ensure only a single connection to the cluster.

What’s the recommended best practice for handling this type of architecture?

Thanks - H

Look at this thread

1 Like