Does anyone have any experience with the C # MongoDB C ++ driver (v2 +) with singleton-style connection / assembly examples in terms of connection stability?
Problem
We recently made an attempt to protect our wider infrastructure, mainly working on SSL, even domestically. Thus, we recently provided one of our primary MongoDb clusters. One of the most immediate differences was the increase in the cost of connecting to the cluster. Our previous solution corresponded to a typical repository template, by means of which the subscriber to the message created an instance of the repository, as well as a new connection, before allowing him GCd after processing this message. We saw a rather significant decrease in message processing performance as a result of switching to SSL - more than we would honestly expect!
Question (s)
Is there a recommended way to work with IMongoClient, IMongoDatabase, IMongoCollection<T>with respect to items with a long life (weeks / months). Makes it gracefully crafted.
- Certain nodes in the cluster (but the remaining cluster)
- The entire cluster goes offline (for example, a network failure)
- Will setting large timeouts, etc. wise and what influence?
My real understanding is that 1. there should be no problem, as it tries to execute buffering operations in the timeout window and process them as soon as the cluster is available again. 3. largely depends on the memory and timeliness of the operation (something we will need to think about ourselves).
, , , , , , . , , , - - .. ?
,