logoDigital Platform Architect
← Small Enterprise HA Platform

Deployment Blueprint

Kubernetes with ingress/WAF, separate node pools per workload, data services, and shared observability.

Architecture Diagram

WSO2 Small HA Deployment BlueprintRegion ADNS / CDN / WAF / IngressAPI ManagementGateway x2 (HA)Publisher/Portal x2 (HA)IntegrationMicro Integrator x2 (HA)Adapters/WorkersIdentity & AccessWSO2 IS x2 (HA) + DBData / ObservabilityDatabases / Caches (HA)OTel → Prometheus / Grafana / ELK

Infrastructure Architecture

  • Kubernetes Multi-Zone Deployment: Worker nodes distributed across availability zones
  • Ingress & Load Balancing: High-availability ingress controllers with WAF integration
  • Node Pool Separation: Dedicated node pools for different workload types and resource requirements
  • Persistent Storage: High-performance, replicated storage for data persistence
  • Network Architecture: Private networking with controlled ingress/egress and service mesh

Operational Considerations

  • GitOps Deployment: All infrastructure and application deployments managed through Git workflows
  • Auto-scaling: Horizontal and vertical pod auto-scaling based on metrics and schedules
  • Backup & Recovery: Automated backup procedures with tested recovery processes
  • Security Hardening: Pod security policies, network policies, and runtime security
  • Monitoring & Alerting: Comprehensive observability stack with proactive alerting

Implementation Notes

This blueprint provides vendor-neutral guidance that can be adapted to various technology stacks. The patterns and principles shown here apply whether you're using cloud-native solutions, enterprise platforms, or open-source alternatives.

Technology Flexibility: While the logical architecture remains consistent, you can implement these patterns using different technologies based on your organization's requirements, existing investments, and operational preferences.