Connecting APIs to Enterprise Mobile App Dev
summary
Argues that gateways not ESBs must front APIs to enforce OAuth-to-SAML/Kerberos identity mapping, content-attack prevention, visual JSON/XML transformation and monetization, keeping heavy parsing out of backend servers. Recommends HTML5 cross-platform development to avoid per-platform SDK fragmentation and speed deployment. Gives an internal use case: a room-finder built in half an afternoon with an Intel open-source HTML5 tool, backing a legacy SQL/CGI system via the gateway. Notes scale realities: 400 apps with 150 to secure and 200/sec spikes vs 10/sec backend queuing at the gateway.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:34API Management
- 7:55Authentication
- 11:52HTML Tools
- 17:39Gateway
- 18:35Tools
- 20:02Load Balance
- 22:34Content Attack Prevention
- 23:22JSON and XML Type Attacks
- 24:17HTTP Authentication
- 25:22Quality of Service
- 25:53Gateways
- 26:29Summary
related talks
29mOpportunities and Risk in API Management
28mAPI Gateway: critical component of your digital architecture
19mMastering Multi-API Gateways: Strategies for Scale, Security & Success.
27mMaster API Gateways: Boost Your Microservices Strategy
27mEnterprise API management in agile integration
23mDecentralized API Management for Agile Enterprises
26mScaling API Re-Use, Security & Integration Across the Multi-Property Consortia.
34mProxies, Gateways, and Meshes: Cloud Connectivity 101 for...