Software architecture styles and patterns

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Definitions[edit]

An architectural pattern is a general, reusable solution to a commonly occurring problem in software architecture within a given context. Architectural patterns are often documented as software design patterns.

"An architectural pattern is a named collection of architectural design decisions that are applicable to a recurring design problem, parameterized to account for different software development contexts in which that problem appears."[1]

Following traditional building architecture, a 'software architectural style' is a specific method of construction, characterized by the features that make it notable" (Architectural style). "An architectural style defines: a family of systems in terms of a pattern of structural organization; a vocabulary of components and connectors, with constraints on how they can be combined."[2]

"An architectural style is a named collection of architectural design decisions that (1) are applicable in a given development context, (2) constrain architectural design decisions that are specific to a particular system within that context, and (3) elicit beneficial qualities in each resulting system."[1]

Some treat architectural patterns and architectural styles as the same,[3] some treat styles as specializations of patterns. What they have in common is both patterns and styles are idioms for architects to use, they "provide a common language"[3] or "vocabulary"[2] with which to describe classes of systems.

The main difference is that a pattern can be seen as a solution to a problem, while a style is more general and does not require a problem to solve for its appearance.

Catalog of architectural patterns[edit]

Catalog of architectural styles[edit]

Structure[edit]

Shared memory[edit]

Messaging[edit]

Adaptable systems[edit]

Distributed systems[edit]

References[edit]

  1. ^ a b R. N. Taylor, N. Medvidović and E. M. Dashofy, Software architecture: Foundations, Theory and Practice. Wiley, 2009.
  2. ^ a b M. Shaw and D. Garlan, Software architecture: perspectives on an emerging discipline. Prentice Hall, 1996.
  3. ^ a b http://msdn.microsoft.com/en-us/library/ee658117.aspx