Lessons learned -- two years with Trafiklab
summary
Trafiklab runs a cloud proxy on AWS (Ireland) with Bangalore devops that exposes legacy SOAP APIs as REST, does SOAP→REST, XML→JSON transforms, adds caching, quotas and key handling, and it attracts 1,500 developers and 600 projects in 18 months. Latency via the Ireland hop, session/load‑balancer mismatches and corporate firewall IP restrictions create real operational pain, and quick fixes in the proxy become long‑term maintenance debt. A hackathon with 21 finalist teams produces a usable app that pairs stranded riders with human helpers and wins startup attention.
AI-written summary · about
chapters (7)
- 0:00Trafiklab introduction
- 3:43Driving principles
- 5:55Technical setup
- 8:25Proxy and API challenges
- 13:06Proxy fixes lessons
- 14:31Developer engagement
- 17:10Q&A
related talks
13mAPIs in the public transport industry — what's next?
35mBeyond Inbound: Unlocking the Secrets of API Egress Traffic Management.
14mRevolutionize Traffic Management with Open APIs: Learn How!
46mLet’s have some effective REST!
48mTransforming a monolith to an API platform
54mAPI's a drivers for innovative business models
24mtfl.fyi: Building Human-consumable APIs
26mWrite Once, Earn Anywhere – Monetizing Enterprise APIs with Cloud Foundry