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 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
- Multitier architecture
- Domain-driven design
- Blackboard pattern
- Monolithic application
- Pipes and filters
- Event-driven aka implicit invocation
- Asynchronous messaging
- Client-server (multitier architecture exhibits this style)
- Shared nothing architecture
- Space-based architecture
- Object request broker
- Representational state transfer (REST)
- Cloud computing patterns 
- Garlan, David (1994). An introduction to software architecture. School of Computer Science, Carnegie Mellon University. OCLC 32160929.
- Haberle, T. (201x). "The Connected Car in the Cloud: A Platform for Prototyping Telematics Services". IEEE Software. 32 (6): 11–17. doi:10.1109/MS.2015.137. S2CID 6722642.