# chanakaudaya/solution-architecture-patterns architecture

> Architecture diagram of the GitHub repository chanakaudaya/solution-architecture-patterns, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-08-14). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/chanakaudaya/solution-architecture-patterns
- Repository: https://github.com/chanakaudaya/solution-architecture-patterns

## Overview

#### Purpose and Entry Point
This is a documentation repository of reusable enterprise solution-architecture patterns and reference architectures, not an executable application. The primary navigation and entry point is `README.md`, which directs readers to Markdown pattern documents grouped by scope. Content is licensed under CC BY 4.0 (`LICENSE`).

#### Content Organization
The repository’s architecture is a curated taxonomy:
- Vendor-neutral reusable patterns: `vendor-neutral/README.md`
- Industry/domain reference architectures: `industry-specific/README.md`
- Vendor-specific implementations and terminology: `vendor-specific/`
- Technology evaluation guidance: `technology-selection-guides/README.md`

Markdown documents are the source of truth; adjacent `images/` directories provide supporting diagrams.

#### Vendor-Neutral Foundation Patterns
`vendor-neutral/` describes cross-platform architectural building blocks: API security and connectivity, identity, integration, deployment, governance, and modernization. Core documents include:
- `vendor-neutral/API-led-Connectivity-Pattern.md`
- `vendor-neutral/Event-Driven-Architecture-Pattern.md`
- `vendor-neutral/Enterprise-Software-Stack.md`

These establish conceptual boundaries between consumers, APIs, services, integration/messaging, data, and operational platform capabilities.

#### Service, API, and Security Boundaries
Several patterns define how enterprise systems expose and protect services:
- `vendor-neutral/API-Security-Pattern.md`
- `vendor-neutral/Centralized-Identity-Access-Management-Pattern.md`
- `vendor-neutral/Microservices-Security-Pattern-Policy-Based.md`

The documented control flow generally places identity/authentication, authorization policy, and API management at ingress or service boundaries before business services access downstream systems.

#### Integration and Event Flows
Synchronous API composition and asynchronous integration are separate but complementary concerns:
- `vendor-neutral/Hybrid-Integration-Pattern.md`
- `vendor-neutral/Event-Driven-Architecture-Kafka-Pattern.md`
- `vendor-neutral/Introduction-to-Change-Data-Capture.md`

These materials cover API-mediated connectivity, event streaming through Kafka, and database-originated change propagation. External infrastructure discussed includes API gateways/managers, Kafka, and integration platforms; they are reference technologies rather than deployed repository dependencies.

#### Deployment and Modernization
Platform and migration concerns are documented as patterns rather than implemented infrastructure:
- `vendor-neutral/Kubernetes-Deployment-Pattern.md`
- `vendor-neutral/Istio-Service-Mesh-Pattern.md`
- `vendor-neutral/Cloud-Migration-Strangler-Pattern.md`

The intended flow is legacy or existing capabilities behind controlled migration boundaries, progressively replaced by modern services deployed on Kubernetes, optionally connected and secured through a service mesh. Multi-cloud and hybrid API-management variants extend this boundary to multiple environments.

#### Domain and Vendor Realizations
Industry documents specialize the generic patterns for business domains, such as health, retail, energy, automotive, and telecommunications:
- `industry-specific/Digital-Health-Platform-Open-Source-Architecture.md`
- `industry-specific/Telecommunication-reference-architecture-pattern.md`
- `industry-specific/future-retail-a-business-and-technical-architecture.md`

Vendor directories map the concepts to platform-specific services and deployment approaches. WSO2 is the deepest vendor-specific collection, especially API management, integration, security federation, and Kafka-connected systems:
- `vendor-specific/wso2/patterns/APIM-EI-Deployment-Reference-Architecture-AWS.md`
- `vendor-specific/wso2/patterns/Event-Driven-Real-Time-Information-System-Kafka-WSO2.md`
- `vendor-specific/aws/AWS-Networking-In-a-Nutshell.md`

#### Selection Guides
Decision-oriented documents compare platform categories rather than prescribe a single stack:
- `technology-selection-guides/API-Management-Platform-selection-guide.md`
- `technology-selection-guides/Integration-Platform-selection-guide.md`

They form the selection boundary between vendor-neutral architectural requirements and concrete API-management or integration-platform choices.

Main entry points: [`vendor-neutral/Enterprise-Software-Stack.md`](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Enterprise-Software-Stack.md) (Enterprise software stack), [`industry-specific/README.md`](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/industry-specific/README.md) (Industry reference catalog), [`vendor-neutral/API-Security-Pattern.md`](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/API-Security-Pattern.md) (API security), [`vendor-neutral/Event-Driven-Architecture-Kafka-Pattern.md`](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Event-Driven-Architecture-Kafka-Pattern.md) (Kafka event streaming)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_entry["Repository entry"]
  node_readme["Repository navigation<br/>Markdown index<br/>[README.md]"]
  node_license["CC BY 4.0 license"]
end

subgraph group_foundation["Vendor-neutral patterns"]
  node_vendor_index["Vendor-neutral catalog<br/>Markdown index<br/>[README.md]"]
  node_enterprise_stack["Enterprise software stack<br/>reference pattern"]
  node_api_connectivity["API-led connectivity<br/>integration pattern"]
  node_api_security["API security<br/>security pattern"]
  node_identity_access["Centralized IAM<br/>identity pattern"]
  node_policy_security["Policy-based microservice security<br/>security pattern"]
  node_hybrid_integration["Hybrid integration<br/>integration pattern"]
  node_event_architecture["Event-driven architecture<br/>event pattern"]
  node_kafka_events["Kafka event streaming<br/>event pattern"]
  node_cdc["Change data capture<br/>data integration pattern"]
  node_modernization["Strangler migration<br/>modernization pattern"]
  node_kubernetes["Kubernetes deployment<br/>deployment pattern"]
  node_service_mesh["Istio service mesh<br/>platform pattern"]
end

subgraph group_realizations["Reference realizations"]
  node_industry_index["Industry reference catalog<br/>Markdown index<br/>[README.md]"]
  node_health_reference["Digital health reference<br/>domain reference architecture"]
  node_telecom_reference["Telecom reference<br/>domain reference architecture"]
  node_retail_reference["Future retail reference<br/>domain reference architecture"]
  node_wso2_realizations["WSO2 pattern realizations<br/>vendor reference patterns"]
end

subgraph group_selection["Technology selection"]
  node_selection_index["Selection guide catalog<br/>Markdown index<br/>[README.md]"]
  node_api_selection["API management selection<br/>decision guide"]
  node_integration_selection["Integration platform selection<br/>decision guide"]
end

node_readme -->|"navigates to"| node_vendor_index
node_readme -->|"navigates to"| node_industry_index
node_readme -->|"navigates to"| node_selection_index
node_vendor_index -->|"organizes"| node_enterprise_stack
node_enterprise_stack -->|"defines API layer"| node_api_connectivity
node_enterprise_stack -->|"defines integration layer"| node_hybrid_integration
node_enterprise_stack -->|"defines messaging layer"| node_event_architecture
node_api_connectivity -->|"protects exposed APIs"| node_api_security
node_api_security -->|"uses authentication"| node_identity_access
node_api_security -->|"enforces authorization policy"| node_policy_security
node_hybrid_integration -.->|"complements with async events"| node_kafka_events
node_event_architecture -->|"realized with"| node_kafka_events
node_cdc -->|"publishes changes to"| node_kafka_events
node_modernization -->|"moves modern services to"| node_kubernetes
node_kubernetes -.->|"optionally connected by"| node_service_mesh
node_industry_index -->|"specializes patterns"| node_health_reference
node_industry_index -->|"specializes patterns"| node_telecom_reference
node_industry_index -->|"specializes patterns"| node_retail_reference
node_enterprise_stack -.->|"informs domain realizations"| node_industry_index
node_api_connectivity -.->|"mapped to vendor implementation"| node_wso2_realizations
node_kafka_events -.->|"mapped to vendor implementation"| node_wso2_realizations
node_selection_index -->|"contains"| node_api_selection
node_selection_index -->|"contains"| node_integration_selection
node_api_security -.->|"supplies requirements"| node_api_selection
node_hybrid_integration -.->|"supplies requirements"| node_integration_selection

click node_readme "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/README.md"
click node_license "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/LICENSE"
click node_vendor_index "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/README.md"
click node_enterprise_stack "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Enterprise-Software-Stack.md"
click node_api_connectivity "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/API-led-Connectivity-Pattern.md"
click node_api_security "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/API-Security-Pattern.md"
click node_identity_access "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Centralized-Identity-Access-Management-Pattern.md"
click node_policy_security "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Microservices-Security-Pattern-Policy-Based.md"
click node_hybrid_integration "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Hybrid-Integration-Pattern.md"
click node_event_architecture "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Event-Driven-Architecture-Pattern.md"
click node_kafka_events "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Event-Driven-Architecture-Kafka-Pattern.md"
click node_cdc "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Introduction-to-Change-Data-Capture.md"
click node_modernization "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Cloud-Migration-Strangler-Pattern.md"
click node_kubernetes "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Kubernetes-Deployment-Pattern.md"
click node_service_mesh "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Istio-Service-Mesh-Pattern.md"
click node_industry_index "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/industry-specific/README.md"
click node_health_reference "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/industry-specific/Digital-Health-Platform-Open-Source-Architecture.md"
click node_telecom_reference "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/industry-specific/Telecommunication-reference-architecture-pattern.md"
click node_retail_reference "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/industry-specific/future-retail-a-business-and-technical-architecture.md"
click node_wso2_realizations "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-specific/wso2/patterns/APIM-EI-Deployment-Reference-Architecture-AWS.md"
click node_selection_index "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/technology-selection-guides/README.md"
click node_api_selection "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/technology-selection-guides/API-Management-Platform-selection-guide.md"
click node_integration_selection "https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/technology-selection-guides/Integration-Platform-selection-guide.md"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_readme,node_license toneBlue
class node_vendor_index,node_enterprise_stack,node_api_connectivity,node_api_security,node_identity_access,node_policy_security,node_hybrid_integration,node_event_architecture,node_kafka_events,node_cdc,node_modernization,node_kubernetes,node_service_mesh toneAmber
class node_industry_index,node_health_reference,node_telecom_reference,node_retail_reference,node_wso2_realizations toneMint
class node_selection_index,node_api_selection,node_integration_selection toneRose
```

## Components

### Repository entry

- [Repository navigation](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/README.md): Markdown index · Primary entry to the pattern taxonomy. · `README.md`
- [CC BY 4.0 license](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/LICENSE): license · `LICENSE`

### Vendor-neutral patterns

- [Vendor-neutral catalog](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/README.md): Markdown index · `vendor-neutral/README.md`
- [Enterprise software stack](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Enterprise-Software-Stack.md): reference pattern · Defines consumers, APIs, services, integration, data, and operations layers. · `vendor-neutral/Enterprise-Software-Stack.md`
- [API-led connectivity](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/API-led-Connectivity-Pattern.md): integration pattern · `vendor-neutral/API-led-Connectivity-Pattern.md`
- [API security](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/API-Security-Pattern.md): security pattern · Places identity, authorization, and API management at service ingress. · `vendor-neutral/API-Security-Pattern.md`
- [Centralized IAM](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Centralized-Identity-Access-Management-Pattern.md): identity pattern · `vendor-neutral/Centralized-Identity-Access-Management-Pattern.md`
- [Policy-based microservice security](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Microservices-Security-Pattern-Policy-Based.md): security pattern · `vendor-neutral/Microservices-Security-Pattern-Policy-Based.md`
- [Hybrid integration](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Hybrid-Integration-Pattern.md): integration pattern · `vendor-neutral/Hybrid-Integration-Pattern.md`
- [Event-driven architecture](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Event-Driven-Architecture-Pattern.md): event pattern · `vendor-neutral/Event-Driven-Architecture-Pattern.md`
- [Kafka event streaming](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Event-Driven-Architecture-Kafka-Pattern.md): event pattern · `vendor-neutral/Event-Driven-Architecture-Kafka-Pattern.md`
- [Change data capture](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Introduction-to-Change-Data-Capture.md): data integration pattern · Propagates database-originated changes into event flows. · `vendor-neutral/Introduction-to-Change-Data-Capture.md`
- [Strangler migration](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Cloud-Migration-Strangler-Pattern.md): modernization pattern · Progressively replaces legacy capabilities behind migration boundaries. · `vendor-neutral/Cloud-Migration-Strangler-Pattern.md`
- [Kubernetes deployment](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Kubernetes-Deployment-Pattern.md): deployment pattern · `vendor-neutral/Kubernetes-Deployment-Pattern.md`
- [Istio service mesh](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Istio-Service-Mesh-Pattern.md): platform pattern · `vendor-neutral/Istio-Service-Mesh-Pattern.md`

### Reference realizations

- [Industry reference catalog](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/industry-specific/README.md): Markdown index · Domain-specific realizations of generic patterns. · `industry-specific/README.md`
- [Digital health reference](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/industry-specific/Digital-Health-Platform-Open-Source-Architecture.md): domain reference architecture · `industry-specific/Digital-Health-Platform-Open-Source-Architecture.md`
- [Telecom reference](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/industry-specific/Telecommunication-reference-architecture-pattern.md): domain reference architecture · `industry-specific/Telecommunication-reference-architecture-pattern.md`
- [Future retail reference](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/industry-specific/future-retail-a-business-and-technical-architecture.md): domain reference architecture · `industry-specific/future-retail-a-business-and-technical-architecture.md`
- [WSO2 pattern realizations](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-specific/wso2/patterns/APIM-EI-Deployment-Reference-Architecture-AWS.md): vendor reference patterns · Deepest vendor-specific collection for API, integration, federation, and Kafka. · `vendor-specific/wso2/patterns/APIM-EI-Deployment-Reference-Architecture-AWS.md`

### Technology selection

- [Selection guide catalog](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/technology-selection-guides/README.md): Markdown index · `technology-selection-guides/README.md`
- [API management selection](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/technology-selection-guides/API-Management-Platform-selection-guide.md): decision guide · `technology-selection-guides/API-Management-Platform-selection-guide.md`
- [Integration platform selection](https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/technology-selection-guides/Integration-Platform-selection-guide.md): decision guide · `technology-selection-guides/Integration-Platform-selection-guide.md`

## Connections

- Repository navigation → Vendor-neutral catalog: navigates to
- Repository navigation → Industry reference catalog: navigates to
- Repository navigation → Selection guide catalog: navigates to
- Vendor-neutral catalog → Enterprise software stack: organizes
- Enterprise software stack → API-led connectivity: defines API layer
- Enterprise software stack → Hybrid integration: defines integration layer
- Enterprise software stack → Event-driven architecture: defines messaging layer
- API-led connectivity → API security: protects exposed APIs
- API security → Centralized IAM: uses authentication
- API security → Policy-based microservice security: enforces authorization policy
- Hybrid integration → Kafka event streaming: complements with async events
- Event-driven architecture → Kafka event streaming: realized with
- Change data capture → Kafka event streaming: publishes changes to
- Strangler migration → Kubernetes deployment: moves modern services to
- Kubernetes deployment → Istio service mesh: optionally connected by
- Industry reference catalog → Digital health reference: specializes patterns
- Industry reference catalog → Telecom reference: specializes patterns
- Industry reference catalog → Future retail reference: specializes patterns
- Enterprise software stack → Industry reference catalog: informs domain realizations
- API-led connectivity → WSO2 pattern realizations: mapped to vendor implementation
- Kafka event streaming → WSO2 pattern realizations: mapped to vendor implementation
- Selection guide catalog → API management selection: contains
- Selection guide catalog → Integration platform selection: contains
- API security → API management selection: supplies requirements
- Hybrid integration → Integration platform selection: supplies requirements