Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (18)
Semelhante a Enterprise API Adoption Patterns
Semelhante a Enterprise API Adoption Patterns (20)
Mais de Akana
Mais de Akana (16)
Último
Último (20)
Enterprise API Adoption Patterns
- 1. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. Enterprise API Adoption Patterns Laura Heritage @heritagelaura
- 2. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. APIs – Extend the Reach of your Business
- 3. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. 4 Adoptions Patterns Accelerate Drive Monetize Analyze APIs • 4 External Innovation • 3 Partner • 2 Mobile • 1 Internal
- 4. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. Internal API Adoption API API API Consume 3rd Party APIs APIBanking Investments Credit Card Lending API API API APIs Across LoBs API API API APIs Within LoB Simplify Acquisitions APIs
- 5. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. Internal - APIs Within LoB API API API • Private APIs and Services • Known Consumer – Manual Consumption • Can be highly sensitive data • How do you build the right level of API / Service • How do you manage your atomic services and the APIs that you produce and consume within your LoB? • How do you plan for growth and innovation? • How do you protect your data? • Creates flexibility in the architecture • Improves teams ability to respond to changes
- 6. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. Internal - APIs Across LOB APIBanking Investments Credit Card Lending API API API • Private APIs • Known Consumer - Self- Service Consumption • Business Relationship • Can be highly sensitive data • How do you manage the APIs you consume from other LoBs? • How do you enforce quality and standards required by the different LoBs? • How do you manage the consumption of your APIs by other LoBs? • How do you protect your data? PCI? • Increase adoption rate of shared resources • Consistent customer experience across LoBs • Improves ability to change and grow business
- 7. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. Internal - Consume 3rd Party APIs API API API • Public APIs • Business Relationship – Self Service • Do you know which external 3rd Party APIs are being used within your organization or company? • How do your procure them? Credit card? Corporate Procurement? • How do you manage the relationship of the APIs which you consume? Are they PCI compliant? • Fulfills capabilities you do not provide internally • Faster time to market
- 8. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. Internal - Simplify Acquisitions • Private APIs • Business Relationship – Manual • How long does a system stay in acquisition mode? • Does a system ever get retired? • Streamline acquisition integrations
- 9. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. API For Mobile Internal / Employee Mobile Apps External Mobile API Platform 3rd Party Mobile App Developer Internal Mobile App Developer APIAPI API • Private and Public APIs • Business Relationship – Manual and Automatic • Increases flexibility in your mobile strategy • Lower cost of your mobile strategy • Lower development effort • Consistent experience across mobile, web and applications • How are you going to secure the API and App? • How are you going to onboard the developers • How will you manage the versions? Every mobile strategy should have APIs at its base
- 10. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. Partner APIs Adoption Keeping Pace with CompetitorsFaster Connections Partners Demanding ItReduce Screen Scraping
- 11. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. API Partner Connections API Platform APIAPI API • Private APIs • Known Consumer - Self- Service Consumption • Business Relationship • How do you quickly on board the partners? • How do you manage the terms and conditions with each partner • Do you need to Scope the API per Partner? • Do you need to Certify the App when it’s built? • Do you need to provide a sandbox environment? • Faster connection to partners • Growth of partner ecosystem • Improved partner / customer experiences
- 12. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. API External Innovation API Platform APIAPI API Developers • Public APIs • Unknown Consumer - Self- Service Consumption • Business Relationship • Which and how much of your resources do you expose? • How are you going to monetize? • How are you going to drive adoption? • How are you going to onboard? • How are you going to secure and protect your backend enterprise? • How are you going to scale? • Drives innovation • Establishes your company as a platform • Increases partner ecosystem • Provides / Increases revenue
- 13. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. Business Impact Of API Adoption Patterns BUSINESS RELATIONSHIP FULLFILLMENT POTENTIAL BUSINESS IMPACT REALISTIC BUSINESS IMPACT PRIVATE (CUSTOM Within LoB) Manual (internal) Manual None None PRIVATE (SELF-SERVE Across LoB / Mobile) Automatic (internal) Automatic High (for big companies) Medium PARTNER Manual Automatic High High PUBLIC Automatic Automatic Very High Medium @andreaskrohn
- 14. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. Internet of Things – Emerging API Adoption Pattern Can’t spell internet of things without APIs • IoT and Wearables connect to one or more APIs Real-Time Interactions Challenges Can be Abstracted by APIs • Authentication • Authorization / Delegated Access • Bandwidth & Display Restrictions • Monitoring Analytics • Data slimming & aggregation • Data sharing User Data Sharing
- 15. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. The API Lifecycle Plan Build RunShare Analyze
- 16. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. Reference Architecture Plan Build Run Share Analyze
- 17. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. API Platform Capabilities Platform Licensing Quota Mgmt. Partner Mgmt. PCI Compliance Provisioning Policy Mgmt. Monitoring OAuth Federation Analytics Lifecycle API/Services Application User Compliance Integrations Gateway Security Authentication Protection IAM Integration Encryption Mediation Quality of Service Paging/Caching Orchestration Scripting API Portal Search Documentation Groups Social
- 18. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. Our Capabilities Streamlined for Efficiency Plan Build Run Share Analyze
- 19. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. Flexible Deployment Model
- 20. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved. API and SOA Resources • Resource Center – http://resource.soa.com/ • Webinar Recording – http://resource.soa.com/resource/webinars • Follow us on: www.facebook.com/soasoftware www.linkedin.com/company/soasoftware @soasoftwareinc
Notas do Editor
- Hello everyone thank you for joining the call today. I am laura heritage. I am a principal solution architect for Enterprise API Platforms. I have been working with companies all over the world for the past 10 years establishing AP and SOA strategies. Today I am going to share my experiences on API Management Adoption Patterns. You can follow me on twitter @heritagelaura
- We have all hear about the explosion in the API Economy. The promises APIs brings when opening up your business. But what are enterprises really doing in this space is a common question. Even just a few months ago, I have talked to enterprises who say they are just not ready, not mature enough to go completely external. Or even that is not there busines. So How are enterprises getting started.
- There are four main adoption patterns I am seeing right now. Internal, Mobile, Partner and External Innovation. As you can see APIs are largely being adopted within the enterprises. We will walk through each of these adoption patterns to understand the drivers for the adoption.
- Lets start with Internal Adoption. Within Internal Adoption there are several different use cases / scenarioes and they are typically based on maturity. Lets go into details of each one of these scenarios
- Most Enterprises do not get a clean slate to start from. The lucky ones have a well definite SOA initiative or a good understanding of SOA principles and practices from which they can extend. But a large majority of enterprises have to contend with hundred of not well designed services and move forward from there. The Internal – APIs within an LOB often brings up the SOA vs API discusses and the services vs API debate. I think now the debates has settled down and realized APIs are an extension of SOA. That service management and API management solution should converge. In the interest of time that is all I will say on this matter. What do APIs inside the enterprise look like? They are typically private APIs and/or service You typically know the consumer and the consumption is manual. Typically they are used point to point and with only one consumer. They can be highly sensitive data. What are the drivers / benefits? Common concerns
- This is where the promise of SOA is being realized through APIs. APIs are making it easier to consume across LOB. API Platforms that are in the market today help make the consumption easier but also help socialize the quality and provide trust amongst LOB. I also think there as been a shift in the not invented here syndrome as well. Where it is now “cool” to reuse and invent on top.
- This Adoption pattern is more about the enterprise as the consumer of APIs. It is the fastest growing and presents unique challenges.
- I separated out Mobile from internal consumption as it has unique characteristic and is a large driver for external APIs.
- Use examples from WestJest and screen scraping the travel agents do. Use example from best buy about the partners forcing them to do it Use an example from First Data on keeping pace with developers
- If your wearable doesn’t have an API you are creating a silo and not participating in the IoT. The true internet of this happens when users are able to selectively share their data.