Transform the internal it landscape with APIs
1 like•209 views
The document discusses the transformative role of APIs in modern IT infrastructure, highlighting their impact on integrations, agility, and customer engagement across various sectors, including examples from Schiphol Airport and Campbell’s Soup. It emphasizes treating APIs as products to drive organizational capabilities and improve development cycles, illustrated by KeyBank's experience in reducing release times through container management. The document concludes with insights on the future importance of API management, agile integration, and Red Hat’s commitment to being a long-term partner in this space.
Transform the internal it landscape with APIs
- 1. Transforming the Internal IT Landscape with APIs Steven Willmott, Senior Director and Head of API Infrastructure August. 2018 @njyx, [email protected]
- 2. Microservices, Containers, APIs & Integration Days 20182 EXAMPLE RED HAT 3SCALE CUSTOMERS Customer Depth and Breadth - One of the Largest API Management Vendors Globally.
- 3. 3 COMMON CHALLENGES IN MODERN IT INFRASTRUCTURE Integrate SaaS Apps Extend Legacy Apps Customer and Partner Access IoT Devices and Architectures Enable Customer Facing Apps via Many Channels Data Access for Business Users
- 5. Microservices, Containers, APIs & Integration Days 2018 What do APIs Really Do? 5 Provide Stable Reusable Interfaces
- 6. Microservices, Containers, APIs & Integration Days 20186 MOST COMMON API USE-CASES Mobile & IOT Support Customer Integration Partner Ecosystem Internal Agility APIs as a Business Content & Transaction Channel
- 7. Microservices, Containers, APIs & Integration Days 2018 Lines between Internal and External APIs are Blurring 7
- 8. 8 INTEGRATION AND APIs DRIVE AIR TRAVEL INNOVATION ● Schiphol Airport aims for world class traveller experiences ● Using Red Hat JBoss Fuse to create the right API endpoints and then putting them in the hands of partners creates an extended team to deliver innovation ● Flight, baggage, reservation, and other data are available throughout the airport and to all partners ● APIs through API Management provide the foundation for seamless handoff between the airport and its partners APIs - Well defined, re-usable, and well managed end-points - Ecosystem leverage
- 9. 9 CAMPELL’S SOUP: APIs LEAD TO A BREAKTHROUGH NEW CUSTOMER CHANNEL ● Initially created a Nutrition and Recipies API to be used by marketing agencies and application designers ● Reaching new audiences with the recipie application “Campell’s Kitchen” on the Amazon Echo device. ● Very high value brand interaction in the customers’ residence. ● Leading to possible Integration with Amazon shopping cart to provision for recipes APIs - Partner Marketing Resource to IoT Backend - Now Powers Campell’s Kitchen
- 10. 10 UNIVERSITY CALIFORNIA AT BERKELEY - INTERNAL AND EXTERNAL APIS ● API Central Program ● Student and Study information, University Core Systems APIs ● But also filtered access to external APIs such as Dropbox, Google Maps to provide an extensive list of APIs ● Platform for new applications in the student body as well as new new inter-department integrations APIs and Organization - IT Organization but... - Providing Student Access - New Apps and Mashups
- 11. Microservices, Containers, APIs & Integration Days 201811 EXAMPLE CURRENT CUSTOMERS All current customers: Depth and Breadth.
- 12. HOW DO WE ACTUALLY SUCCEED?
- 13. Microservices, Containers, APIs & Integration Days 2018 1. Focus on True Value 2. Enable rather than Own 13
- 14. Microservices, Containers, APIs & Integration Days 201814 THE API OWNER’S MANUAL ● Captured learning from successful API teams ● Reinforced by recent experience ● Digital Copy: https://engage.redhat.com/3scale-api-ow ners-s-201706160312
- 15. #1 Focus on True Value
- 16. Many initiatives, all urgent, all intersecting, all conflicting
- 17. Jeff Bezos moment? https://plus.google.com/+RipRowan/posts/eVeouesvaVX (http://bit.ly/SWGA-B)
- 18. 18 Outcomes Thor Mitchell / Google / Crowdcube DesirableUndesirable Expected Unexpected Design Fire Drill Innovation Prohibited
- 19. M ajor platform investm ents Little initial traction Revisited all processes EXAMPLE: MAPS CREDIT UNION
- 20. Understand the Jeff Bezos moment: change the way you work, not the infrastructure you have
- 21. #1 Focus on True Value #2 Enable rather than Own
- 22. Bimodal IT ...
- 23. “Gartner’s Recipe for Disaster” - Jason Bloomberg / Forbes “Gartner’s Bimodal IT considered harmful” - Phil Wainwright / Diginomica “This is akin to adding lipstick to the pig” - Simon Wardley / CSC
- 24. Fundamental misunderstanding of Bimodal IT that it was about slowing down one of the Modes
- 25. Actually it is about creating stability between the modes
- 29. Platform Team Platform Enablement Team
- 30. Encourage deployment but… Provide Technology Guidance Impose Stability Requirements Require Lifecycle Statements Enforce Documentation Standards Enforce Security Standards In other words ensure stability
- 31. Create the right environment… Automation is Key Treat as a Capability to run APIs Treat APIs as Products
- 32. 32 KEYBANK: SIMPLIFYING AND ACCELERATING DEVELOPMENT CYCLES ● Long development cycles. Small under-resourced release team and a wide range of compliance checks required ● Container deployment and management across a broad set of developers. Shrank release times from 2-3 months to 1 week ● Also empowered more people to act and release - key effect on organizational dynamics Containers - Retooled development and deployment entirely - Broader availability and faster rollouts
- 33. Lesson: Enable the platform versus owning the platform
- 34. Millions of devices syncing Robust libraries & dev collaboration Randomized back off EXAMPLE: FITBIT Jeremiah Lee, San Francisco, 2016
- 36. #1 Help move the puck #2 Enable rather than own Bonus: What to Measure?
- 37. Bad Metrics Number of APIs Number of API Calls Number of Integrations Number of Containers Number of Servers Number of Lunch & Learns
- 38. Good Metrics Number of Apps Supported Number of complete Use Cases Number of Users Dollar Value of Business Speed of Application development Speed of API Deployment
- 39. TAKE AWAYS...
- 40. Microservices, Containers, APIs & Integration Days 2018 ● Incremental transformation ● Creating a new organizational capability ● Treating APIs as products rather than resources 40
- 41. Microservices, Containers, APIs & Integration Days 201841 THANK YOU FOR YOUR TIME! ● APIs will very likely be a key architectural component for most organizations ● Red Hat is investing heavily and aiming to be a long term partner ● Agile Integration, Container Management and API Management will be a key architectural pillars for the next 3-5 years
- 42. Microservices, Containers, APIs & Integration Days 201842 FOLLOW UP MATERIAL ● Red Hat Integration homepage: https://www.redhat.com/en/technologies/jboss-middleware/integrate ● “Inside mind of a successful platform architect / Gartner APPS 2016” https://www.slideshare.net/3scale/inside-mind-of-a-successful-platfor m-architect-gartner-apps-2016 ● “API Model Canvas for successful API strategies and programs” https://www.slideshare.net/3scale/api-model-canvas-for-successful-ap i-strategies-and-programs ● “The API Owner’s Manual” https://www.redhat.com/en/resources/3scale-api-owners-manual-ebo ok
- 43. THANK YOU & Q&A! Steven Willmott [email protected], @njyx