Samtrafiken - Lessons learned from Trafiklab
0 likes2,221 views
The document discusses lessons learned from two years with Trafiklab, highlighting the importance of dialogue and lower thresholds for user interaction. It details the API structure, including transformations and proxy systems, and mentions the engagement of 1500 developers across 600 projects. The focus is on improving accessibility and error management within the API framework.
1 of 25
More Related Content
What's hot (16)
Ad
Viewers also liked (7)
Ad
Similar to Samtrafiken - Lessons learned from Trafiklab (20)
More from Nordic APIs (20)
Recently uploaded (20)
Samtrafiken - Lessons learned from Trafiklab
- 1. Lessons learned – 2 years with Trafiklab
- 2. 20/03/2013 2
- 3. Lars Löfquist Technical Chief Trafiklab lars.lofquist@samtrafiken.se 127.0.0.1 2013-03-20 3
- 5. 2013-03-20 5
- 7. Dialogue. Lower Thresholds. Showroom.
- 8. Dialogue. .
- 10. Showroom. .
- 12. api.trafiklab.se Proxy API-owner API-owner
- 13. Friendly error messages TRANSFORMATIONS Proxy - SOAP REST - XML JSON Hide part of responses KEY - Authorization CACHE - Quota
- 16. API-owner Proxy
- 17. Server 1 Load balancer Session ! Proxy Server 2 Session ?
- 18. Server 1 Load balancer Proxy Session Server 2
- 19. Firewall Applikation Proxy
- 20. Proxy
- 21. api.trafiklab.se Proxy Backen API
- 24. 1500 developers. 600 projects.