architectural pattern Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

subject > pattern > architectural pattern

Next pattern: design pattern Up: pattern Previous pattern: software architecture

architectural pattern comparison table

Subject use allow increases facilitate has definition reduce contain is a synonym of distribute have advantage anticipate

broker an object to call methods of another object without knowing that this object is remotely located reuse because you may be able to reuse remote objects that others have created divide and conquer since the remote objects can be independently designed An architectural pattern in which parts of the system are transparently distributed to different nodes of a network a solution that has been proven to effectively solve the problem in the indicated context aspects of the software system to different nodes

multi-layer to build a multi-layer system replacement of a layer by an improved version, or by one with a different set of capabilities reusability because the lower layers can often be designed generically so that they can be used to provide the same services for different systems divide and conquer since the separate layers can be independently designed An architectural pattern in which a system is divided into layers coupling since well-designed lower layers do not know about the higher layers a solution that has been proven to effectively solve the problem in the indicated context obsolescence: databases and UI systems tend to change; by isolating these in separate layers, the system becomes more resistant to obsolescence

pipe and filter a pipeline you to design flexible systems using components that are as independent of each other as possible reuse because it is often possible to find reusable components to insert into a pipeline designing for testability because it is normally easy to test the individual processes An architectural pattern in which data in a standard format is passed through a series of processes (filters) that transform it in some way coupling because the processes have only one input and one output, normally using a standard format a solution that has been proven to effectively solve the problem in the indicated context transformational architecture the system can be modified easily by adding or changing the transformational processes

transaction-processing you to design flexible systems using components that are as independent of each other as possible divide-and-conquer since the design of each handler can be given to separate software engineers An architectural pattern in which a transaction dispatcher inputs transactions and dispatches them to handlers a process which reads a series of inputs describing a transaction one by one, and a transaction handler that decides what to do with each transaction, and which dispatches a procedure call or message to a component that will handle the transaction

Subject	use	allow	increases	facilitate	has definition	reduce	contain	is a synonym of	distribute	have advantage	anticipate
broker		an object to call methods of another object without knowing that this object is remotely located	reuse because you may be able to reuse remote objects that others have created	divide and conquer since the remote objects can be independently designed	An architectural pattern in which parts of the system are transparently distributed to different nodes of a network		a solution that has been proven to effectively solve the problem in the indicated context		aspects of the software system to different nodes
multi-layer	to build a multi-layer system	replacement of a layer by an improved version, or by one with a different set of capabilities	reusability because the lower layers can often be designed generically so that they can be used to provide the same services for different systems	divide and conquer since the separate layers can be independently designed	An architectural pattern in which a system is divided into layers	coupling since well-designed lower layers do not know about the higher layers	a solution that has been proven to effectively solve the problem in the indicated context				obsolescence: databases and UI systems tend to change; by isolating these in separate layers, the system becomes more resistant to obsolescence
pipe and filter	a pipeline	you to design flexible systems using components that are as independent of each other as possible	reuse because it is often possible to find reusable components to insert into a pipeline	designing for testability because it is normally easy to test the individual processes	An architectural pattern in which data in a standard format is passed through a series of processes (filters) that transform it in some way	coupling because the processes have only one input and one output, normally using a standard format	a solution that has been proven to effectively solve the problem in the indicated context	transformational architecture		the system can be modified easily by adding or changing the transformational processes
transaction-processing		you to design flexible systems using components that are as independent of each other as possible		divide-and-conquer since the design of each handler can be given to separate software engineers	An architectural pattern in which a transaction dispatcher inputs transactions and dispatches them to handlers		a process which reads a series of inputs describing a transaction one by one, and a transaction handler that decides what to do with each transaction, and which dispatches a procedure call or message to a component that will handle the transaction

Next pattern: design pattern Up: pattern Previous pattern: software architecture