Scribd
Upload
56 views

Architectural Styles Repositories

Repository architecture is a style where all data in a system is managed in a central repository that is accessible to all components. The components interact only through the repository, not directly with each other. There are two types of components - the central repository which stores the shared data, and independent subsystems that operate on the data in the repository. Examples where this style is used include software development environments, databases, and blackboard systems for problems like speech recognition.

Uploaded by

Enson KY
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
56 views

Architectural Styles Repositories

Repository architecture is a style where all data in a system is managed in a central repository that is accessible to all components. The components interact only through the repository, not directly with each other. There are two types of components - the central repository which stores the shared data, and independent subsystems that operate on the data in the repository. Examples where this style is used include software development environments, databases, and blackboard systems for problems like speech recognition.

Uploaded by

Enson KY
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 16

Architectural

Styles
Repositories
Repositories
• Subsystems access and modify data from a single data structure called the
repository, also called blackboard architecture
• Repository architecture is a collection of independent components which
operate on central data structure.

• Subsystems interact only through the repository

• Control flow is dictated by the repository through triggers or by the


subsystems through locks and synchronization primitives
All data in a system is managed in a central repository that is accessible to all
system components. Components do not interact directly, only through the
repository
The knowledge sources: make changes to the shared
Components
• In a repository style there are two quite distinct kinds of components
i. a central data structure represents the current state.
Shared data is held in a central database or repository and may be
accessed by all subsystems

ii. a collection of independent components operate on the central


data store.
Each sub-system maintains its own database and passes data
explicitly to other sub-systems.
• Examples of repository architectures include blackboard
architectures, where a blackboard serves as communication centre
for a collection of knowledge sources, and database systems serving
several applications Repositories are very important for data
integration, are being introduced in a variety of applications, including
software development, CAD etc
• The choice of control discipline leads to major subcategories.
• If the types of transactions in an input stream of transactions trigger
selection of processes to execute, then the repository can be a
traditional database.(repositories)
• If the current state of the central data structure is the main trigger of
selecting processes to execute, the repository can be a blackboard.
Data- Centred
• Strengths:
 Efficient way to share large amounts of data
Data integrity localized to repository module

Weaknesses:
Subsystems must agree (i.e., compromise) on a repository data model
Schema evolution is difficult and expensive, for larger subsystems
 Distribution can be a problem
Blackboard architecture
• Interactions between the repository and its external components can
vary significantly between systems
• The blackboard model is usually presented with three major parts:
i. The knowledge sources: make changes to the shared data that lead
incrementally to solution
ii. The blackboard data structure: problem-solving state data, organized
into an application-dependent hierarchy. Knowledge sources make
changes to the blackboard that lead incrementally to a solution to
the problem.
iii. Control shell: is driven entirely by the state of the blackboard
Blackboard architecture
Examples
• Repository: modern compilers act on shared data: symbol table, abstract
syntax tree

• example of an IDE where the components use a repository of system design


information. Each software tool generates information which is then
available for use by other tools. When used You should use t
Examples
• Blackboard:
• signal and speech processing, pattern recognition
• Batch sequential systems with a global database
• Programming environment
Repository Architecture style use
• Complex interpretation of signal processing such as speech and
pattern recognition
• Batch sequential systems working with a global database
• Programming environment- a lot of programming modules uses this
kind of architectural style
Advantages of Repository Architecture Style
• Components can be independent—they do not need to know of the
existence of other components. Changes made by one component can
be propagated to all components. All data can be managed consistently
(e.g., backups done at the same time) as it is all in one place.
• Repository Architecture Style provides data integrity, backup and
restore features.
• It reduces overhead of transient data between software components.
• It has an efficient way to store large amount of data.
• It has a centralized management which consists of backup, security and
concurrency control.
Disadvantages
• The repository is a single point of failure so problems in the repository
affect the whole system. May be inefficiencies in organizing all
communication through the repository.
• Distributing the repository across several computers may be difficult
• In repository architecture style, evolution of data is difficult and
expensive.
• It has high dependency between data structure of data store and its
software components or clients.
• End

You might also like