Data architecture for fetch-intensive database applications

An apparatus comprising

• a first database;
• and
• a second database including materialized views over said first database, said first and second databases being such that a majority of updates are performed more efficiently to said first database than they would be if said updates were to be performed to said second database, and a majority of reads are performed more efficiently from said second database than they would be if said reads were to be performed from said first database, at least one of said materialized views being based on at least one read specific to an application, said application being an on-line fetch processing application such that:
• a) most transactions are read-only;
• b) most of the read-only transactions use key-based selections and
• c) substantially all transactions are defined at system design time;
• wherein a majority of updates to said second database are performed via at least one technique of view maintenance.

A telecommunications switch comprising

• a first database;
• and
• a second database including materialized views over said first database,
• wherein a majority of updates to said second database are performed via at least one technique of view maintenance.

A telecommunications switch comprising

• a first database;
• and
• a second database including materialized views over said first database, the first and second databases being such that a majority of updates are performed more efficiently to said first database than they would be if said updates were to be performed to said second database, and a majority of reads are performed more efficiently from said second database than they would be if said reads were to be performed from said first database, at least one of said materialized views being based on at least one application-specific read;
• wherein propagation of said majority of updates to said second database is performed via at least one technique of incremental view maintenance, the processing associated with said view maintenance being substantially performed at said first database.