What’s not to like about IBM API Management?
Jackie Zhu 1100007DBS email@example.com | | Tags:  redbooks api management apim
0 Comments | 4,123 Visits
Chris Wood is an Integration Architect at Visa Europe, based in the United Kingdom. Chris has a background in SOA and ETL, designing and building systems that incorporate WebSphere SOA Appliances, WebSphere Service Registry and Repository and WebSphere MQ.
I like to get stuff done. I can’t help it. This is just part of my personality. I like to get to grips with a problem, work out the best way to solve it and get it done. I think this is why I was drawn into integration architecture and design. For the past ten years, I’ve been taking integration problems and attempting to solve them, to get them done right.
People who have worked with me will also know that eventually I like to talk. It may take a while to get going, but once I get there with a problem and how to solve it, suddenly take-off velocity is reached and there’s no stopping me.
That continuing dialogue, taking a problem, working out how to solve it, and communicating the solution particularly resonates with me on the subject of Web APIs. I’ve only been in the API space for a couple of years but I understand the value of Web APIs and what they bring to the integration space:
This is where IBM API Management can help; it provides the tools to the integration guy to make stuff happen, to get Web APIs into the marketplace and get developers working with them ASAP. With IBM API Management you can:
So IBM API Management helps businesses, developers and the integration guy deliver Web APIs. What’s not to like? Don't forget to check out the IBM Redbooks publication on IBM API Management to learn more!
For IBM API Management related blog posts, see:
For IBM API Management Redbooks publication, see: