Weitere ähnliche Inhalte Ähnlich wie The Business Value for Internal APIs in the Enterprise (20) Kürzlich hochgeladen (20) The Business Value for Internal APIs in the Enterprise1. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
The Business
Value for Internal
APIs in the
Enterprise
Laura Heritage
@heritagelaura
laura.heritage@soa.com
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.
But How Do You Extend Your Reach If Your
Internal House is Not In Order?
#1 Reason for an Enterprise to Not Have an External API
We are Not Mature Enough
4. 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
5. 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
6. 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
7. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
APIs are and Extension Of SOA
Approach Level
• API – Are a product which can have a direct or
indirect tie to revenue.
• SOA Services – Are utilized to make an
enterprise more agile to break down the
business process into composable parts.
Consumption Level
• APIs tend to have larger number of consumers
and focuses on ease of consumption through
self service
• SOA Services tends to have well known
consumers and fewer of them and usually has a
more detailed on-boarding processes.
Governance & Management Level
• API – Focuses on product management tasks
• SOA – Focuses on organization changes and
standard approaches
Technical Level
• API and SOA - Requires similar runtime
management capabilities
The Gartner document is available upon request.*Gartner, Inc., Magic
Quadrant for Application Services Governance by Paolo Malinverno,
Daryl C. Plummer, Gordon Van Huizen, August 8th 2013.
Gartner Magic Quadrant 2013
Application Services Governance
8. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
APIs Extend the Value of Apps and Services
Transform
& Secure
Publish Monetize
Dev.
Adoption
API
SOAP to REST
Mobile-
Optimization
OAuth
Mediation
Analytics API Documentation
Applications
and Services
Apps
API Producers API Consumers
9. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
Today: API as a Feature Of the Product
The Product
APIs
Features
Reports
HA
Audit
Credit
Check
Loan
Approval
Loan
Inquiry
Loan
Origination
Application Interface
10. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
Tomorrow: Move to API is the Product
The Product
Features
Reports
HA
Audit
Credit
Check
Loan
Approval
Loan
Inquiry
Loan
Origination
API
An API FIRST Approach
11. 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
12. 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
13. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
Two Emerging API Architecture Patterns
1.Unified API Gateway
2.Unified API Gateway with Purpose Built ESB
14. 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
15. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
Difference Between ESB and API Gateway
ESB API Gateway
System to System Integration Securely Expose, Protect and
Encrypt API/Services
Includes many Adapters Light Weight Integration
Strongly Message Oriented Light Weight Orchestration
Heavy Business Process
Management and Event Processing
Policy driven
Transaction Role back Caching
Code centric Configuration /Scripting Centric
16. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
Unified API Gateway
Legacy systems /
App Servers/
Systems of Record
API Gateway
Interfaces
Implementations
MQ /Other Protocols
Applications
JSON/XML
Security
Protection
Encryption
Authentication
QofS
Quota
Caching
Mediation
Internal/ External
End User
Protocol Conversion
Orchestration
Messaging
Message Exchange
Mainframe
App
Server
17. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
A Unified API Gateway is A Good Place To Start
• Simplified architecture
• Light weight
• Lower skill level need to deploy, run and manage
• Policy driven through configuration
• Endpoints are standardized
• Quick return on investment
18. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
Purpose Built ESB Might be Necessary When:
• You already have an ESB in your architecture
• There is purpose built ESB that has legacy system adapters that
will make your life easier
• Need assured delivery with transaction role back capabilities
• Off load expensive message processing
• Complex Orchestrations and Event processing
• Separation of concerns in architecture (interface /
implementation)
19. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
Unified API Gateway with Purpose Built ESB
Legacy systems /
Systems of Record
API Gateway Interfaces
ImplementationsESB
REST /SOAP
MQ /Other Protocols
Applications
JSON/XML
Security Orchestration
QofS Caching
Encryption
Mediation
Assured Delivery
Message Exchange
Protocol Conversion
Complex Event Processing
Messaging
Protection
mainframe
App
Server
Internal/ External
End User
20. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
Caution
• Be careful if you want to start by putting in a purpose built ESB
first if you don’t already have one.
• You may never reach the Unified API Gateway level due to the
complexity of setting up the ESB.
21. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
A Unified SOA & API Platform Become
Increasingly Important
• Measure the impact of
your programsAnalytics
• Build your developer
and partner ecosystem
Developer
Engagement
• Secure and protect
your systemsGateway Services
• Simplify and speed up
development
Service
Integration
• Build the right services
& APIs the right way
Lifecycle
Management
22. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
Auditing, Monitoring, Analytics
Typical SDLC Flow
Portfolio
Management
Lifecycle
Management
Policy
Manager
API Gateway
Community
Management
Planning
EA/BPM
tools
Repository Registry
SCCMs
TFS/VS
Developer
Portal
API & Service
Exposure
23. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
API Gateways For Internal and External Use
24. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
Most Enterprises Are Still Developing In Silos
Enterprise Architecture Teams / CoEs
Unable to effectively reach their internal or external consumers
25. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
Remove the Silo’d Barriers to Enable an Internal
Developer Community
26. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
Create More Effective Applications To Reach Even
More of Your Consumers
27. Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.Copyright © 2001-2013 SOA Software, Inc. All Rights Reserved.
Extend the Reach of Your Enterprise Beyond
Your Boarders
“Reach
Consumers in
ways you can’t
even dream of”
Start with your internal developer community today!
28. 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
Hinweis der Redaktion 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. In my last webinar a few weeks ago I introduced Enterprise API Management Adoption Patterns. Today I am going to focus on the Internal Adoption pattern
You can follow me on twitter @heritagelaura
APIs bring the promise of Extending the reach of your business, enabling you to reach your consumers in ways you haven’t even dreamed of yet. They enable you to get to cloud, mobile and IoT. Or so they promise too. But how do you Extend your reach if your internal house is not in order? When I speak with enterprises about APIs, they all say they need to get there, but most say we are not mature enough to have an API. But like with most, the term APIs and an “external” connotation to it now. As I mentioned earlier, 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. When we take a look at house APIs are adopted within the enterprise the there are several different use cases / scenarios. They are typically based on maturity.
In my webinar a few weeks ago I introduced this Business Impact of API Adoption Patterns. For very large companies the potential business impact is High when adopting APIs. Realistically it is going to initially be a medium business impact. However, once your internal house is in order it will be much easier to obtain the High and Very High impact of the Partner and Public APIs Isn’t this just SOA? How do you move from point custom APIs to the higher value APIs that can be consumed in a self service fashion? Talk about cloud integration vendors. During