Handle Dynamic Connection Strings

[sambhavyadav90]

We need to handle dynamic connection strings. The idea is that different clients of our Web API need to have different databases. We want that when client A makes a request to the Web API, database X is used; & when a client B does the same, then database Z is used

[UdhayarajanJ]

In above mentioned the issues. comes under the multitenancy while they are give the request capture the which type client through middleware or pipeline then make an object that particular repository.

[rajibmahata]

In a multi-tenant Web API, where each client uses a separate database, it’s crucial to dynamically determine the correct database connection string based on the client making the request. Initially, we considered using middleware to handle this, but middleware logic runs when the application starts, not during individual requests. At that time, we don’t have access to client-specific information, such as request headers, which makes it unsuitable for dynamic connection string resolution.

To address this, we implemented a Tenant Identification Service. This service is designed to extract the client information from the incoming request during runtime. Specifically, we use the HTTP header X-Client-ID to identify the client. For this example, two clients—ClientA and ClientB—are supported, each mapped to its own database connection string. The service validates the client identifier and retrieves the appropriate connection string dynamically.

Pls have a look one the pull request : #22