Scoped repository/multitenancy about mongodb-generic-repository HOT 2 OPEN

I suspect the advice relates to the connection pooling in the mongo driver itself.

Issues with connection exhaustion normally only show themselves when a system is having to serve many requests at once. Registering as Scoped results in spinning up a new connection pool with every request being processed by your server. This will slow the processing of each request and if the server is taking a lot of traffic it could quickly run into re-source constraints.

As a suggestion to solve the scenario of a multi-tenant system with a database per tenant, it might be better to build and register a IMongoRepositoryFactory that creates the IMongoRepository singletons and caches the instances against some reference for each tenant. That way the problems that a scoped registration would give can be avoided.

from mongodb-generic-repository.

@attilabicsko - I am trying to do the same thing. Did you implement it successfully? How did you made
builder.Services.AddIdentity<ApplicationUser, ApplicationRole>()
.AddMongoDbStores<>(...) to work? Since inside this extension method it always assumes one connection strings. To me it feels like I have to change certain parts of AspNetCore.Identity.MongoDbCore as well.

Any thoughts?

from mongodb-generic-repository.