0

I'm trying to implement a way to have multiple databases (identical databases, all have same tables etc.) but I need them to be separate thus multiple DBs. Is there a way to have a single DBContext and repository pattern that can interact with all of them (who have different connection strings) from the controller.

(all the DBs are the same just different DB name)

Ex. I have 3 controllers/endpoints api/course1 , api/course2, and api/course3 Each course has a database. I've been looking at various documentation but having difficulty on how I can have it done with a repository pattern.

Thank you!

dylan solaman
  • 41
  • 1
  • 1
  • 7

1 Answers1

1

Yes, you can use different connection strings based on current request. In your startup.cs, change the code to configure DbContext to something similar to this example:

 services.AddDbContext<ApplicationDbContext>((serviceProvider, options) =>
        {
            var httpContext = serviceProvider.GetRequiredService<IHttpContextAccessor>().HttpContext;
            var routeData = httpContext.GetRouteData();
            string connectionString;
            // insert here code to determine connection string based on route data.
            options.UseSqlServer(

                connectionString
            );
        });

Here I am using Dependency Injection to get information about current request and route data to determine the connection string. You can use any service you want and any logic you want to determine the connectionString.

Then when the ApplicationDbContext is injected in your repository class or your controller it will use that connection string for that request.

Sherif Elmetainy
  • 4,034
  • 1
  • 13
  • 22
  • I think that's exactly it that I'm looking for. I do want to inject it (I have an entity repository project), how would I get the type `api` endpoint there, a parameter next to options? – dylan solaman Sep 08 '20 at 19:59
  • Cool, this should work. I'm going to remove my answer – Hintham Sep 08 '20 at 20:00
  • You can parse the URL of the http context, or use route data. It depends on your controller. RouteData contains a dictionary of route value like "action", "controller", etc. You can use that to determine which endpoint and parameters are used. – Sherif Elmetainy Sep 08 '20 at 20:45
  • I see, this is a new way to me but will look into it, thanks! – dylan solaman Sep 08 '20 at 22:26