chanakaudaya/solution-architecture-patterns

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.