Repository Architecture Style
In Repository Architecture Style, the data store is passive and the clients (software components or agents) of the data store are active, which control the logic flow. The participating components check the data-store for changes.
A client sends a request to the system to perform actions (e.g. insert data). The computational processes are independent and triggered by incoming requests. If the types of transactions in an input stream of transactions trigger selection of processes to execute, then it is traditional database or repository architecture, or passive repository. This approach is widely used in DBMS, library information system, the interface repository in CORBA, compilers, and CASE (computer aided software engineering) environments.
Repository Architecture Style
Advantages
Repository Architecture Style has following advantages −
Provides data integrity, backup and restore features.
Provides scalability and reusability of agents as they do not have direct communication with each other.
Reduces overhead of transient data between software components.
Disadvantages
Because of being more vulnerable to failure and data replication or duplication, Repository Architecture Style has following disadvantages −
High dependency between data structure of data store and its agents.
Changes in data structure highly affect the clients.
Evolution of data is difficult and expensive.
Cost of moving data on network for distributed data.