# chanakaudaya/solution-architecture-patterns

Reusable, vendor-neutral, industry-specific, vendor-specific solution architecture patterns for enterprise

Repository: https://github.com/chanakaudaya/solution-architecture-patterns
Canonical: https://ross.abutalabs.com/products/solution-architecture-patterns
Homepage: https://chanakaudaya.github.io/solution-architecture-patterns/
License: CC-BY-4.0
License Family: other
Topics: solutions-architect, solutions-engineering, enterprise-architecture, enterprise-software, api-gateway, integration, security, solutions-architecture, architecture-patterns, architecture, reference-architecture
Last push: 2023-04-17T05:29:49+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 2707, "days_push": 1234, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 3465, forks 675 (observed 2026-08-28T04:08:05.769286+00:00)

## What it is
A curated collection of reusable solution architecture patterns for enterprise software systems, covering vendor-neutral, industry-specific, and vendor-specific designs. It documents patterns like API security, microservices, event-driven architecture, and cloud migration, and accompanies a published book.

## Use cases
- find reference architectures for enterprise integration
- learn microservices and API management patterns
- design an API security architecture
- plan a cloud migration using the strangler pattern
- compare event-driven architecture options with Kafka or NATS
- study service mesh and Kubernetes deployment patterns

## When to choose
- you need vendor-neutral reference architectures for enterprise system design
- you are a solutions architect studying established and emerging integration patterns
- you want conceptual blueprints before choosing concrete technologies

## When to avoid
- you need runnable code or deployable templates rather than written patterns
- you want tooling or automation instead of documentation
- you need deeply maintained, frequently updated technical content

## Facets
- artifact type: learning-resource
- maturity: maintenance
- function: documentation, api-gateway, security, microservices, developer-tools
- domain: developer-tools, documentation, apis, cloud-computing, microservices, security
- platform: cross-platform
- tags: architecture-patterns, enterprise-architecture, reference-architecture, solution-architecture, api-management, integration-patterns, awesome-lists, devops

## Member repositories
- chanakaudaya/solution-architecture-patterns (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:05.769286+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:36:52.484199+00:00, confidence not recorded.
  - readme: https://github.com/chanakaudaya/solution-architecture-patterns (fetched 2026-08-28T04:08:05.769286+00:00, sha 871d167872f6)
  - homepage: https://chanakaudaya.github.io/solution-architecture-patterns/ (fetched 2026-08-29T09:31:10.757519+00:00, sha 8fa6bb111e8c)
- Data as of 2026-08-30T08:39:29.467469+00:00.