Difference between revisions of "Architecture Styles"
From Suhrid.net Wiki
Jump to navigationJump to search (Created page with "= Intro = * It is a pattern of component types and their interactions. * Define constraints: how things are allowed to interact. * Architectural pattern is synonym for style. *...") |
(→Intro) |
||
| Line 9: | Line 9: | ||
** Connectors: e.g how are they connected ? RPC, Data stream ? | ** Connectors: e.g how are they connected ? RPC, Data stream ? | ||
** Constraints: On components - e.g. data store cant modify itself, On connections - no P2P communication allowed. | ** Constraints: On components - e.g. data store cant modify itself, On connections - no P2P communication allowed. | ||
| + | |||
| + | = Data Centred = | ||
| + | |||
| + | * Characterised by the access/update of a central data store. | ||
| + | * E.g. Transactional DB, Blackboard, CASE Tools. | ||
Revision as of 04:26, 4 April 2012
Intro
- It is a pattern of component types and their interactions.
- Define constraints: how things are allowed to interact.
- Architectural pattern is synonym for style.
- Defining features:
- Component types: e.g data store, processes etc.
- Component layout: e.g. which process is allowed to access data store.
- Connectors: e.g how are they connected ? RPC, Data stream ?
- Constraints: On components - e.g. data store cant modify itself, On connections - no P2P communication allowed.
Data Centred
- Characterised by the access/update of a central data store.
- E.g. Transactional DB, Blackboard, CASE Tools.
