Aggregate Storage
- 2 minutes to read
The aggregate storage component was implemented to overcome limitations of a single scheduler storage. The scheduling information can now be stored in multiple storages simultaneously.
Benefits of the aggregate storage:
Different types of scheduler storages – bound (TcxSchedulerDBStorage) and unbound (TcxSchedulerStorage) – can be bound to the scheduler simultaneously.
Since aggregate storage components can be linked to each other, you can build multilevel data sets.
The aggregate storage automatically merges data from bound storages and transfers it to the scheduler.
Scalable data structure:
Large storages can be split into smaller storages that can contain more specific data – you might want to use one storage for all-day user events, one – for holidays, and another – for tasks.
Smaller storages simplify data reuse in other applications.
More flexibility when modifying existing structures used by the scheduler. Since data can be split between any number of storages, the data dependency can be minimized this way. As a result, to make changes to the data layer in order to better suit business tasks, new storages can be added to the data layer, or existing storages can be removed from the data layer without affecting the other storages. This also requires minimal changes to code thanks to using the TcxSchedulerAggregateStorage.OnEventInserting event.
Balance between storage performance and data maintenance. Multiple storage architecture allows you to achieve optimum data handling performance, and at the same time minimize efforts on maintaining the underlying data (for instance, when performing back up, or localizing data inconsistency).