Loading Search...

API Best Practices Blog

Case Study: SaaS API Governance and Management »

Last week, Tim Madewell of Innotas gave a great case study presentation on SaaS API Governance and Management at the Burton Group Catalyst conference.

The key point:  If you provide or use a SaaS API, you have to make sure your SaaS API has the same level of governance as on-premise alternatives.  And if you can nail this - you might have a significant competitive advantage over both your on-premise and SaaS competitors in your vertical.

Tim talks about the evolution of their API becoming an critical part of the service, the importance of governance, and how they operationalized their API.   

TrueCredit.com API case study »

Scott Metzger, CTO of TrueCredit.com was kind enough to take some time to talk about their Consumer Connect API program and some of the technical challenges that they have addressed using Apigee's API Gateway.

Scott wanted to make life easier on his development team as they ramped up their number of APIs, partners and traffic volumes.  Here, he describes how he uses the technology as a 'policy layer' to provide API analytics, fine-grained data protection, and caching in an API Gateway. In this case, Apigee Enterprise is deployed on-premise virtualized software.

 

We're very excited to be working with Scott and TrueCredit, and check out the full TrueCredit Case study

SaaS API management and operations »

We often find that our customers find new and intersting ways to express the importance of having visibility and control over an API.   Below is a great example - a recent case study we did with Tim Madewell, VP of Engineering of Innotas -  the leading IT Governance SaaS provider -  talks about how they leverage and operationalize their SaaS API for competitive advantage.
From a competitive standpoint, Tim makes a great point that it's critical to be able to assure enterprise customers that a SaaS API is as robust as anything their customer could build or buy on-premise - not only from a functional standpoint, but operationally in terms of security, compliance, control and scale.   
From a technical stanpoint - Tim talks about the importance of having separation,  visibility, and control between front-end Web app and back-end service traffic.  We are seeing this use case more often as more web products are being built off the same API that is opened to customers and partners.
Check out this use case video and for more from Tim and Innotas, Dana Gardner did a great podcast on Innotas at briefingsdirect.com (link to - http://www.sonoasystems.com/about-us/news-and-events/innotas-api-infrastructure-for-visibility-and-control)

This week we'll be at the O'Reilly Velocity conference on scalability and operations in San Jose.   On the topic of API operations, below is a case study we did with Tim Madewell of Innotas, providers of on-demand IT Governance -  where he talks about how they operationalize and scale their SaaS API.

Tim talks about the importance of having separation and visibility between front-end and back-end service traffic.  We are seeing this use case more often as more web products are being built off the same API that is opened to customers and partners.  Because your web app is the biggest customer of the API, it's critical to be able to understand and throttle traffic into the back-end to make sure your web app performance isn't compromised by API usage by other clients. 

From a competitive standpoint, Tim makes a great point that it's critical to be able to assure enterprise customers that a SaaS API is as robust as anything their customer could build or buy on-premise - not only from a functional standpoint, but operationally in terms of security, compliance, control and scale.   

For more on this, Dana Gardner did a great podcast on Innotas API management at briefingsdirect.com