Key Tips for Your On-Premise Hybrid API Success
summary
Builds an active‑active on‑prem hybrid API platform across two sites using Azure API Management self-hosted Gateway on four OpenShift clusters, required to survive a total cloud outage and go live in under three months. Design takes ~6 weeks, build 6–8 weeks, expect a 5–6 month project and two dedicated cross‑skilled builders. Operations use Prometheus on PVC, Filebeat shipping to ELK, ingress sharding, and 500,000 calls with 32 errors demonstrates >99.99% success.
AI-written summary · about
chapters (13)
- 0:00On-premise hybrid API platforms
- 1:31On-premise vs cloud
- 5:30Enterprise build challenges
- 7:57Project overview
- 10:50Key build tips
- 12:39Solution architecture
- 14:27Infrastructure considerations
- 16:54Kubernetes best practices
- 19:26Network access & security
- 21:33Network security design
- 23:41Monitoring & logging
- 26:29Go-live results
- 27:34Resources & portal
related talks
01h 03mCreating a hybrid and multi-cloud strategy using Azure API Management
01h 00mLessons from the API Management Trenches
28mAPI Management the hybrid way
11mHow To Scale Infrastructure
22mHybrid cloud, extend your on-premises infrastructre?
29mThe API Gateway Maturity Matrix: Where Do You Rank?
05mOn Prem is the new Black
06mSwitching to On-Premise - The When and the Why