Beyond Inbound: Unlocking the Secrets of API Egress Traffic Management.
summary
Workshop demonstrates a control plane that routes outgoing calls through a lunar proxy and an interceptor, surfaces visibility for five API providers and 11 endpoints, and autogenerates fixes as plugins. A demo applies strategy-based throttling and quota policies (policy.yaml) to shift traffic 50/50 to 80/20, cutting a 65% error spike and 429s down while reporting 78% of calls optimized and more 200s. The system exposes per-endpoint metrics, token-aware rate handling, and live policy apply.
AI-written summary · about
chapters (13)
- 0:00API egress traffic management
- 1:52Ingress vs Egress
- 3:40API producer challenges at scale
- 7:17API consumption basics
- 9:00API consumption problems
- 10:08Rate limits with OpenAI API
- 15:51LunarDev rate limit demo
- 18:20Dark side of API management
- 20:08API consumption visibility
- 23:24API issues with LunarDev plugins
- 28:18Policy-based optimization
- 31:55Why egress traffic matters
- 34:24Closing
related talks
12mThe Next API Frontier: Mastering API Consumption Across Distributed Envts
19mUnleash the Power of API Management Solution
26mWhere API management meets the service mesh
29mTaming the Traffic: Select...
54mFive-step plan for securing your APIs
28mAPI Gateway: critical component of your digital architecture
01h 01mWorkshop: 5 Key API Management Success Strategies You Need Today
31mIn and Out: A 20-Minute Adventure or How to Rewrite a Bank's API Gateway