Software Architecture Patterns logopeterindia.net
Knowledge Hub

Software Architecture Patterns: Catalogs, Cloud Patterns & Books

A learning catalog of software architecture patterns — structural, distributed and cloud patterns, domain-driven design, documentation methods and books.

60 topics•7 categories•Updated October 2026

Pattern Catalogs & References

11 entries

Large collections of architecture and cloud patterns.

Structural & Application Patterns

10 entries

How to organize a codebase and its dependencies.

Distributed & Cloud Patterns

13 entries

Patterns for data, resilience and migration.

Domain-driven Design

4 entries

Modeling complex business domains.

Documenting Architecture

3 entries

Methods for describing and communicating architecture.

Books & Learning

8 entries

Where to read more.

Related Pages

11 entries

Neighbouring pages on this site.

Frequently Asked Questions

What are software architecture patterns?

Architecture patterns are proven, reusable solutions to recurring structural problems in software systems, such as how to layer a codebase, separate reads from writes or keep services resilient to failure.

How do architecture patterns differ from design patterns?

Architecture patterns shape the overall structure of a system or service, while design patterns solve smaller, code-level problems inside it. See the Software Design Patterns page for the code-level view.

Which patterns are most used in cloud systems?

Layered and hexagonal structure inside services, plus CQRS, event sourcing, saga, circuit breaker, sidecar, backends for frontends and the strangler fig for migration.

Where should I start?

Start with a catalog such as the Azure Architecture Center patterns or Martin Fowler's architecture guide, then read the original articles for hexagonal and clean architecture.

How current is this page?

Links were checked in October 2026. Sites that block automated checks (O'Reilly and Baeldung) are kept and may need a manual click. Pattern names and definitions vary between authors, so treat each catalog as one perspective.