from API Survey Cutter Benchmark Review - 2014 (In Partnership with Wipro) Business Drivers IT Drivers More than 70% chose New partnership & Increasing revenue More than 65% chose Application integration, Mobile Integration & device integration
Bench Mar Review - 2014 (In Partnership with Wipro) Close to 70% have API programs underway or in roadmap Close to 60% have API programs owned by IT Insights from API Survey
Risk is number one challenge followed by business model reengineering More than 60% feel all the capabilities listed are important Insights from API Survey
consumption – Flexibility & Ease of Use API Management Authentication & Authorization Token Mediation Routing Analytics & Dashboard Metering & Pricing Community Portal Service Oriented Middleware Applications & Data Sources Transformation Service Orchestration Routing Adapters Connectors Protocol Mediation Sales Servicing Payments Billing Message Mediation • Provider Integration Focused • Interface Granularity aligned towards reuse, provider abstraction • Predominant design based on SOAP, HTTP/JMS • Focused on ease of consumer use • Consumer based policies leading to APIs with easy access of range of consumers • Predominant design based on REST, XML/JSON
Lessons carried to API world • Developer hand-holding on consumer and provider side to enable smooth adoption • Mapping documentation & service invocation framework are important for enterprise wide success • Centralized Repository for discovery, lifecycle management & impact analysis • One size fits all approach to service design does not work • SSO for Services and abstracting security logic from implementation
Platform & Standards • Reference Architecture • Consider all External integration scenarios, business requirements and map products • Address how the API layer integrates with existing enterprise landscape • Look at all integration scenarios (Internal to Internal, External to External, …) to finalize deployment architecture • Focus on Security – Protocols, Token Mediations and IDAM instances for different scenarios • Define Standards for API Development • Process around API governance (Critical if SOA doesn’t exist in the enterprise or maturity is low)
& Ownership • Funding & sponsorship for the platform development, Support of APIs • Fund a core API Team • Consider “API as a Service” deployment Model (to attain cost variabilization) • Consultative engagement with projects to identify API scenarios • API with Partner integration & Mobile have direct business involvement many times and hence ownership
Onboarding • Templates to capture API requirements • Self Service for consumers • Sandbox environments, Virtualization of endpoints • Collaboration Portals & Knowledge sharing forums • Training programs • API Evangelization
& Monitoring • Need quick turn around for production issues – Comprehensive monitoring of services & APIs needed • End to end infrastructure needs to scale • Centralized logging, auditing and metering • Transaction volumes on APIs can quickly increase, leading to explosion of audit logs, potential big data problem