Architectural patterns are often documented as software design patterns. An architectural pattern often uses the same description as a general, reusable solution to a commonly occurring problem in software architecture within a given context.
The separation of what is architectural and what is design is not commonly agreed, nor are the patterns catalogued in any accepted form.
Software Architecture is an ambiguous term which not only relates to the discipline of software architecture itself, but also structure and connections between components.
An Introduction to Software Architecture[1] describes it as such "We are still far from having a well-accepted taxonomy of such architectural paradigms, let alone a fully-developed theory of software architecture. But we can now clearly identify a number of architectural patterns, or styles, that currently form the basic repertoire of a software architect."
Catalog of architectural patterns edit
- Asynchronous messaging
- Blackboard
- Blackboard pattern
- Client-server (multitier architecture exhibits this style)
- Cloud computing patterns
- Component-based
- Database-centric
- Domain-driven designing
- Event-driven aka implicit invocation
- Layered
- Microkernel
- Model–view–controller
- Monolithic application
- Object request broker
- Peer-to-peer
- Pipes and filters
- Presentation–abstraction–control
- Publish-subscribe
- Reflection
- Representational state transfer (REST)
- Rule-based
- Sensor–controller–actuator
- Service-oriented
- Shared nothing architecture
- Space-based architecture
- Strangler fig pattern
References edit
- ^ Garlan, David (1994). An introduction to software architecture. School of Computer Science, Carnegie Mellon University. OCLC 32160929.