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
The Business Value for Internal APIs in the Enterprise