How sap-archive/cap-distributed-resiliency works
Project Type and Purpose
• This is an open-source sample repository providing reference blueprints and code snippets for implementing distributed, active-active resiliency in SAP Cloud Application Programming (CAP) applications on SAP Business Technology Platform (BTP), using either Azure (SAP HANA Cloud + Azure Traffic Manager) or AWS (Amazon Aurora + Route 53).
• There is no single runnable codebase here, but rather two scenario implementations (in separate branches or folders) showcasing best practices for cross-region failover and multi-zone replication.
File Structure
• Top-level files:
• README.md – describes purpose, scenarios, patterns
• LICENSE / LICENSES – licensing details
• CODE_OF_CONDUCT.md – contributor guidelines
• Scenario implementations live in separate branches or subdirectories (e.g., “SAP-HANA-Cloud”, “Amazon-Aurora”), each containing a small CAP service, deployment manifests, infrastructure as code, and step-by-step instructions.
• Other directories (.reuse, .vscode) hold metadata and IDE settings, not core architecture code.
README Insights
• Two primary resiliency scenarios:
a. SAP HANA Cloud cross-zone replication + Azure Traffic Manager for DNS-based geo-load balancing
b. Amazon Aurora read replicas + Amazon Route 53 for active-active database failover
• Emphasizes distributed resiliency patterns on SAP BTP across multiple Availability Zones and regions.
Main Components
a. SAP CAP Application (deployed as microservices on SAP BTP Cloud Foundry or Kyma)
b. API / Application Gateway (SAP BTP API Management or Cloud Foundry router)
c. DNS / Traffic Management Layer (Azure Traffic Manager or Amazon Route 53)
d. Two or more regional deployments (Region A, Region B)
– Each region has:
• CAP microservice instances (multiple AZs)
• SAP HANA Cloud (multi-zone) or Amazon Aurora (primary + read-replica)
e. Inter-region database replication (HANA multi-zone replication or Aurora cross-region replicas)
f. External clients or UIs (SAP Launchpad, web/mobile clients)
Relationships and Interactions
• Client → DNS/TM → region endpoint
• DNS/TM continuously monitors health checks in both regions
• Region endpoint load-balances incoming requests across AZs
• CAP microservices process requests, read/write to local DB
• DB replication ensures data synchronization across regions
• On regional failure, DNS/TM reroutes traffic to healthy region
Architectural Patterns and Principles
• Active-active deployment across regions
• Multi-zone replication within each region
• Health-check-driven DNS failover
• Circuit breaker and retry logic in CAP services
• Infrastructure as Code for reproducible deployments
Key Technologies / Frameworks
• SAP CAP (Node.js or Java)
• SAP BTP Cloud Foundry runtime or Kyma runtime
• SAP HANA Cloud multi-zone replication
• Azure Traffic Manager (Geo, Priority routing)
• Amazon Aurora Global Database / Read Replicas
• Amazon Route 53 health-check failover
• IaC (Terraform/Cloud Formation/Multi-Service YAML)
Detail and Clarity
• Fallback paths and failover cut-over logic.