Core Architecture
High‑throughput core transaction platform with business‑aware global traffic scheduling
10B+
Requests / Day
Multi‑cloud
Active‑Active Regions
< 50ms
P99 Latency
99.99%
Availability
Global Gateway & Traffic Scheduler
Requests enter via edge POPs → APISIX (in‑house extended) / Cloud‑native Gateway MSE → Business‑aware Global Traffic Intelligent Scheduler → regional microservices clusters. Automatic failover across regions/clouds, blue‑green/canary by policy.
Edge POP
APISIX(Internal Extension)
• Plugin Pipeline
• Dynamic Routing
• Rate Limiting & Circuit Breaking
Cloud-Native Gateway MSE
• Managed Elasticity
• Stability Assurance
• Auto Scaling
Business-Aware Global Traffic Intelligent Scheduler
• Intelligent Routing Decisions
• Business Priority Scheduling
• Real-time Performance Monitoring
Asia Pacific
• Microservice Clusters
• Auto Failover
North America
• Microservice Clusters
• Auto Failover
Europe
• Microservice Clusters
• Auto Failover
Failover
Cross-region/Cloud Auto Switch
Release Strategy
Blue-Green/Canary Release
Global Gateway Layer
- APISIX (in‑house extensions) for plugin pipeline & dynamic routing
- Cloud‑native Gateway MSE for managed elasticity and stability
- Business‑aware Global Traffic Intelligent Scheduler (highlight)
- Multi‑cloud / multi‑region failover with health & cost signals
- Blue‑green & canary release with per‑audience targeting
Core Transaction Platform
- Event‑driven microservices; idempotent pipelines; exactly‑once at boundaries
- Real‑time risk control & rate limiting; tokenized sensitive data
- Settlement & reconciliation jobs with backpressure control
- Schema‑versioned contracts; backward‑compatible rollouts
- End‑to‑end tracing across gateway → services → data layer
Traffic Strategies
- Latency‑aware routing with active health checks
- Cost‑aware region weighting; burst absorption
- Risk‑aware throttling for suspicious patterns
- Sticky‑session & geo‑affinity with graceful rebalance
Resilience & Release
- Active‑active across regions/clouds; automated failover
- Circuit‑breaker, bulkhead, retry with jitter backoff
- Blue‑green/canary with error‑budget gates (SLO‑driven)
- Chaos drills and capacity rehearsal on a schedule
SLOs & Targets
- Requests/day: 10B+ (sustained)
- P99 end‑to‑end latency: < 200ms (payments path)
- Gateway P99: < 50ms; Risk pipeline < 80ms
- Availability: 99.99% (quarterly target)
Payment Transaction Flow
Card present/online → gateway → auth → risk → ledger → settlement; outbox/SAGA ensure consistency with retries & dedupe.
Card Present/Online
Gateway
Auth
• Authentication
• Authorization
• Token Validation
Risk
• Risk Assessment
• Fraud Detection
• ML Scoring
Ledger
• Transaction Record
• Audit Trail
• State Management
Settlement
Outbox/SAGA Pattern
• Event Sourcing
• Distributed Transactions
• Saga Orchestration
Consistency & Reliability
• Automatic Retries
• Deduplication
• Idempotency