This document discusses the challenges of integrating mobile applications with backend systems and proposes an API management solution. It notes that different technologies, devices, development cycles and security issues make mobile integration difficult. A reference architecture is presented using an API gateway to mediate communication between mobile apps and backend systems, providing benefits like security, support for different standards and protection of backend investments. The document argues that not having an API strategy is akin to organizations in the 1990s that lacked websites.

1. Interfaces for a connected and mobile world
API Management
Matthias Biehl
2014-06-12

2. 24.06.2014 Seite 2© 2014 [ipt] Switzerland
Business Challenge:
Multiple Channels for External Integration

3. 24.06.2014 Seite 3© 2014 [ipt] Switzerland
API - Application Programming Interface
q
q
q

4. 24.06.2014 Seite 4© 2014 [ipt] Switzerland
Growth of APIs – They work!
Source: ProgrammableWeb.com

5. 24.06.2014 Seite 5© 2014 [ipt] Switzerland
Beware of API Wild West!

6. Technical Challenge: Point to Point Solutions
24.06.2014 Seite 6© 2014 [ipt] Switzerland

7. Solution: API-Management
24.06.2014 Seite 7© 2014 [ipt] Switzerland

8. Benefits of API Management for IT
24.06.2014 Seite 8© 2014 [ipt] Switzerland
IT
• Secure Integration
• Control
• Developer Support

9. Benefits of API Management for the Business
Business
• Multi-Channel
• Niches
• Innovation
24.06.2014 Seite 9© 2014 [ipt] Switzerland

10. 24.06.2014 Seite 10© 2014 [ipt] Switzerland
API Value Chain
Business
Owner
API
App Developer
App
End User
API: Leverage External Innovation!
Business
Asset

11. 24.06.2014 Seite 11© 2014 [ipt] Switzerland
APIs as Driver for External Innovation
“Invention comes in many forms and
at many scales. The most radical and
transformative of inventions are
often those that empower others to
unleash their creativity –to pursue
their dreams.”
Jeff Bezos, amazon

12. APIs support Multiple Channels
Deep Dive Here:
Mobile Channel with APIs

13. Backend
Frontend
Mobile Apps
Mobile Apps
Mobile Apps
Enterprise Backend
Systeme
Technical Challenge in Mobile Integration
24.06.2014 Seite 13© 2014 [ipt] Switzerland

14. Backend
Frontend
IAM Systeme
Mobile Apps
Mobile Apps
Mobile Apps
Management
Consoles
Enterprise Backend
Systeme
Technical Challenge in Mobile Integration
ESB/BPM
DatenbankenLegacy Systeme
24.06.2014 Seite 14© 2014 [ipt] Switzerland

15. Backend
Frontend
IAM Systeme
Management
Konsolen
Enterprise Backend
Systeme
Technical Challenge in Mobile Integration
Currently, the biggest challenge for
enterprise mobile applications is
backend integration.
Enterprise Mobility Report, VDC Research, 09-2013
ESB/BPM
DatenbankenLegacy Systeme
24.06.2014 Seite 15© 2014 [ipt] Switzerland
Mobile Apps
Mobile Apps
Mobile Apps

16. Backend
Frontend
IAM Systeme
Management
Konsolen
Enterprise Backend
Systeme
Technical Challenge in Mobile Integration
Currently, the biggest challenge for
enterprise mobile applications is
backend integration.
Enterprise Mobility Report, VDC Research, 09-2013
“Currently, backend integration
accounts for approximately 30%
[cost, effort] of a typical mobile
initiative”
Enterprise Mobility Report, VDC Research, 09-2013
ESB/BPM
DatenbankenLegacy Systeme
24.06.2014 Seite 16© 2014 [ipt] Switzerland
Mobile Apps
Mobile Apps
Mobile Apps

17. Why is this so difficult?

18. 24.06.2014 Seite 18© 2013 [ipt] Switzerland
Mobile vs Backend: Different Technologies
WebSocket
SOAPXML
REST
JSON

19. 24.06.2014 Seite 19© 2013 [ipt] Switzerland
Mobile vs Backend: Different Devices

20. 24.06.2014 Seite 20© 2013 [ipt] Switzerland
Mobile vs Backend: Different Technology Cycles

21. 24.06.2014 Seite 21© 2013 [ipt] Switzerland
Mobile vs Backend: Development Cultures

22. 24.06.2014 Seite 22© 2013 [ipt] Switzerland
Mobile vs Backend: New Security Exploits

23. Backend
Frontend
Mobile Apps
Mobile Apps
Mobile Apps
Enterprise Backend
Systeme
WebSocket
SOAPXML
REST
Mobile vs Backend: Summary
JSON
24.06.2014 Seite 23© 2014 [ipt] Switzerland

24. Reference Architecture

25. API Gateway
Backend
Frontend
AuthN
AuthZ
IAM
Mobile Apps
Mobile Apps
Mobile Apps
Enterprise Backend
Systeme
Internet
Mobile Integration Reference Architecture
24.06.2014 Seite 25© 2014 [ipt] Switzerland

26. Runtime Sequence

27. 6/24/2014 27
{"jsonrpc": "2.0", "method":
"GetGeoIP", "params": {"IPAddress":
"1.1.1.1"}, "id": 3}
<soapenv:Envelope xmlns:soapenv=“.."
xmlns:web=“..">
<soapenv:Header/>
<soapenv:Body>
<web:GetGeoIP>
<web:IPAddress>1.1.1.1</web:IPAddress>
</web:GetGeoIP>
</soapenv:Body>
</soapenv:Envelope>
<soapenv:Envelope xmlns:soapenv=„.." xm
<soapenv:Header/>
<soapenv:Body>
<web:GetGeoIPResponse>
<web:GetGeoIPResult>
<web:ReturnCodeDetails>Success
<web:CountryName>Switzerland</
</web:GetGeoIPResult>
</web:GetGeoIPResponse>
</soapenv:Body>
</soapenv:Envelope>
{"jsonrpc": "2.0”, "id": "3“, "result": {
"CountryName": "Switzerland",
"ReturnCodeDetails": "Success",
"ReturnCode": "1",
"IP": "1.1.1.1",
"CountryCode": "CH”},
}

28. Policy

30. Technical Benefits

31. 24.06.2014 Seite 31© 2014 [ipt] Switzerland
 Mediation Layer: Separate
Concerns of Business Logic &
Technology
 Security: Protect Client Data
and Business Services
 Efficient Support for
Development and Maintenance
 Protect Investment in Backend
 Support new Mobile Standards
 Clustering - Scalability and
Performance
Benefits od the Mobile Reference Architecture
API Gateway
Backend
Frontend
AuthN
AuthZ
IAM
Mobile AppsMobile Apps
Mobile Apps
Enterprise Backend
Systeme
Internet
API Gateway
API Gateway

32. Not having an API today is like
Not having a Website in the 90s

33. 24.06.2014 Seite 33© 2014 [ipt] Switzerland
Matthias Biehl
Senior Consultant
matthias.biehl@ipt.ch