C＃.NET实体框架多租户最佳实践

Question

Consider the following code segment:

public class DatabaseContext : DbContext
{
   public DatabaseContext(String connectionString) : base(connectionString)
   {            
   }
}

public class ContextNameDatabaseContext : DatabaseContext
{
   public ContextNameDatabaseContext(String connectionString) : base(connectionString)
   {
   }
}

Would one say it is best practice when building the back-end for a multi-tenant solution where each client has its own database and maintain the data state until a user logs out / off?

Developer using these classes in this instance will need to be aware and careful as to when and how the classes are being used where the 'DatabaseContext' class acts as a base to the 'ContextNameDatabaseContext' class.

Please advise on any thoughts or suggestions.

Answer 1

One approach is to keep all the database connection strings as parameters in the database. However you have to assure that its encrypted.

Then at your DB layer you can pass the connection as parameter in plain text after decrypting and constructing your connection string accordingly:

public class MyDatabase: DbContext
{
    public MyDatabase(string connString)
    {
        this.Database.Connection.ConnectionString = connString;
    }
    public DbSet<Order> Orders{ get; set; }
}

You can also use IOptions if you are using .NET Core to inject the connection string as a dependency.