APIStrat Keynote: Lessons in Transforming the Enterprise to an API Platform
3 likes•541 views
This document outlines lessons from transforming an enterprise to an API platform. It discusses 5 key lessons: 1) developing an API strategy, 2) implementing federated API governance, 3) modernizing architecture and delivery, 4) increasing API adoption, and 5) defining platform processes. The goal is to offer a platform that supports internal developers, public app developers, customers, and third-party approved apps through APIs, streams, and events.
APIStrat Keynote: Lessons in Transforming the Enterprise to an API Platform
- 1. Lessons from Transforming the Enterprise to an API Platform 25 Sept 2018 James Higginbotham [email protected] @launchany
- 2. 2@launchany Introduction • Executive API Consultant • API strategy and execution • Across multiple verticals: – Commercial Insurance – Healthcare – Hospitality – Finance and Banking – Travel – Airline
- 3. 3@launchany The Enterprise API Journey
- 4. 4@launchany APIs are the ultimate “do over” for enterprise IT
- 5. 6@launchany The Emerging Enterprise API Platform Offers API Inventory API Orders API Identity API Accounts API Rewards API Partners Internal Developers Public App Developers Customers Third-party Approved Apps
- 6. 7@launchany to support the platform Lesson #1: Develop an API Strategy
- 7. 8@launchany Understand the “Why” of Your API Strategy 1. Accelerate mobile strategy 2. Adapt to changing customer relationships 3. Speed partner integrations 4. Foster technical and business innovation 5. Unsilo channels through easier data sharing
- 8. 9@launchany Understand the “How”: API Design First Process
- 9. 10@launchany Measure the Results of Your API Strategy • Do we have a consistent customer experience across all channels? – An API-centric approach ensures consistency across all channels, while each channel applies API capabilities in the manner best suited for the channel • Are we encouraging co-ownership between IT and business? – Business and IT must work together to deliver a great platform • Are we achieving expected agility (speed and safety in harmony)? – Your goal is to move safely at a higher rate of speed – properly aligned API strategy is the enabler
- 13. 14@launchany to increase platform quality Lesson #2: Implement Federated API Governance
- 14. 15@launchany SOA Governance: Suppressing Innovation Since 2004
- 15. 16@launchany Modern API Program Governance Coaching Guidelines Flexibility
- 16. 17@launchany Choosing Between Centralized and Federated Governance • Centralized – Creates strict consistency across APIs, go/no-go decision for every API created – Reduced throughput, often doesn’t scale • Federated / Hub-and-Spoke – Centralized group steward the standards, produce shared resources – Lends more context to the problem than a centralized group – Better fit for larger organizations or those with distributed workforce • Federated / Independent – Centralized group steward a framework for standards – Teams embrace and extend as needed
- 17. 18@launchany API Portfolio Management is Critical • Define a clear lifecycle for APIs to go from idea to production • Differentiate APIs between private, partner, and public • Bundle APIs to restrict access, enforce entitlements • Establish metrics that define quality APIs
- 18. 19@launchany to optimize for agility Lesson #3: Modernize Architecture and Delivery
- 19. 20@launchany Expose Business and Tech Capabilities Through APIs • Manage project from start to completion • Add collaborators to a project • Subdivide a project into issues • Mark issue complete • View incomplete issues • View active projects • POST /projects • POST /projects/{projectId}/members • POST /issues • POST /issues/{issueId}/completed • GET /issues?status=incomplete • GET /projects?status=active
- 20. 21@launchany Drive Speed and Agility with Microservices + Automation Alexa VoiceSkill API Product API Product Messaging (e.g.Kafka) … Microservice … API … Microservice … API … Microservice … API … Microservice … API Slack Chatbot Web+ MobileApp API Product Team B Team A Messaging (e.g.Kafka)
- 21. 22@launchany Create Opportunity with Event-Driven APIs
- 22. 23@launchany Operationalize Data with Streaming https://engineering.linkedin.com/distributed-systems/log-what-every- software-engineer-should-know-about-real-time-datas-unifying
- 23. 24@launchany Move Your Platform Beyond Request-Response APIs • Events and streaming extend the platform beyond its original design • Discovery via channel definitions using AsyncAPI (asyncapi.com) • Function-as-a-Service (FaaS) will be the glue Rewards API Redeem Svc Register Svc Redemption Stream Redemption Event onRedemptionEvent() APIs Services Streaming & Eventing Functions-as-a-Service & Stream Processors Redemption Processor
- 24. 25@launchany to grow the platform 4. Increase API Platform Adoption
- 25. 26@launchany How We Think of API Consumption
- 26. 27@launchany The Reality of API Consumption Consumption Phase Goal Discovery Identify API capabilities Mapping Map solution to Platform API capabilities using reference documentation Exploration Prototype consumption (“Try-it-out”) Onboarding App registration for API access to testing and staging Integration Developers consume the API within the solution via code Certification Obtain final approval for production API access Usage Monitoring Production usage monitoring and throttling Platform Improvement Request platform API enhancements to meet the needs of the solution Platform Updates Build platform awareness; update notifications for enhancements; sunsetting A great API program assists API consumers through all phases of their consumption journey. This results in a healthy, growing platform instead of a stagnating program.
- 27. 28@launchany API Adoption Maturity Model Level 1: Adhoc Limited or no adoption, no guidance on capabilities provided or how to get started Level 2: Dev Portal Capabilities and API docs offered to teams for reference and shared understanding Level 3: Enablement Apps onboarding and consuming with guidance Level 4: Self-Onboarding Apps are able to onboard with minimal or no guidance Level 5: Community API platform knowledge shared and coached without council guidance
- 29. 30@launchany to accelerate and sustain the platform 5. Define Platform Processes
- 30. 31@launchany Product-Driven. API-Centric • APIs, streams, and events treated as long-lived products • Product owners listen to stakeholders to drive the API roadmap • Objectives and Key Results (OKRs) and KPIs drive improvements • Without a product-driven approach, APIs become stale and anemic, resulting in frustrated customers and developers • Single-most challenging shift for the enterprise (but necessary)
- 31. 32@launchany Operationalizing the Platform Involves Everyone • InfoSec – Review API designs, identify risks, authority to approve/decline apps consuming sensitive endpoints • Platform – Product ownership, roadmapping, marketing/evangelism, drive onboarding consumers, coach teams new to consuming the platform, education (self-serve and workshops, hackathons) • Infrastructure/DevOps – Ensure network, server, container platforms, necessary resources (e.g. message brokers, kafka, etc) are available and can be installed for a new project/team as required • Engineering – Coach teams on common practices, patterns, delivery; onboard new projects that (most likely) consume the platform • Program Management Office – Assist in the overall process of the platform and API initiatives, implement change management
- 32. 33@launchany Apply Cross-Functional API Training
- 33. 34@launchany The API Platform Journey 1. Develop an API strategy to support the platform 2. Implement federated API governance to increase platform quality 3. Modernize architecture and delivery processes to optimize for agility 4. Increase API onboarding and adoption to grow the platform 5. Define platform processes to accelerate and sustain the platform
- 34. 35@launchany The Journey Toward an Enterprise API Platform Offers API Inventory API Orders API Identity API Accounts API Rewards API Partners Internal Developers Public App Developers Customers Third-party Approved Apps Redeem Svc Register Svc Avail Offers Svc Check Inv Svc Ship Receive Svc Create Order Svc Order History Svc Profile Svc Permissions Svc Friends n Fam Svc Redemption Stream New Acct Stream Inv Low Stream Order Proc Stream
- 35. 36@launchany The Future is Integration: No Code, Low Code, and Ephemeral Apps