- ABP Framework version: v8.2.2
- UI Type: Angular
- Database System: MySQL
- Tiered (for MVC) or Auth Server Separated (for Angular): yes
- Exception message and full stack trace:
We are currently experiencing a rapid growth of data in our transactional database, and we expect millions of records to accumulate in the coming days. Given this, we are looking for a way to manage this data effectively without compromising the performance of our transactional operations.
Is there an approach or best practice using ABP Framework with EF Core where we can:
Keep evolving and frequently accessed records in the transactional database. Automatically move unused or historical records to an archival database based on specific criteria (e.g., time-based archiving or status-based archiving).
Specifically, I'm interested in:
Any ABP-specific modules or features that facilitate the management of transactional and archival databases. How we could integrate such an archival mechanism in our existing ABP application using EF Core.
I would appreciate any insights or recommendations on how to achieve this functionality within the ABP ecosystem.
- Steps to reproduce the issue:
3 Answer(s)
-
0
hi
We have no experience in this case.
You can implement such a feature in EF Core, and then ABP will be automatically compatible with it, because ABP completely uses EF Core as the data source.
If you have any problem with this feature and abp. You can give feedback here.
Thanks.
-
0
thank you for your response 👍
-
0
: )
