Periodical Data

[mgochmuradov]

Hi everyone!

Background

We are building a billing application for a MidSize Telecom operator with ABP Community (EFCore, angular).
As there are a lot of operation data (ex: phone calls from one subscriber to another), the customer asked us to make this data archivable.

So we have come up with the following solutions and wanted your opinions.

Option 1: Separate DB

We will create a separate DBContext for this type of data, and possibly use MongoDB for horizontal scaling.

Option 2: Periodic Data

Still with a separate DBContext

• Create a Period Model, UI, and API to manage Periods (with start and end dates, and connection string)
• Introduce an ICurrentPeriod service (similar to ICurrentTenant)
• Introduce an IPeriodicDbContext interface to be applied on DBContext
• Edit DbContextFactory to use the connection string from the selected Period

With this implemented,

• We can archive old data and lock a Period, so only read-only operations will be allowed.
• We can still edit entities (If Period is not locked) and query archived data by changing the current period

using (var period = CurrentPeriod.Switch(periodId))
{
    // Do stuff
}