Public APIs and Utility APIs

Hi All,

Just wanted to know some best practices for API deployment.

When we introduce APIGEE as an API management platform, we will have all public APIs exposed through this platform. Having said this, there may be a large number of private utility APIs as well. What would be APIGEE's recommendation on those APIs? Would you recommend those utilityAPIs also exposed through the management platform? Whats a best practice here?

regards

Vinodh

0 1 312
1 REPLY 1

My view is that if you or your team publishes an API so that it is available to developers who are outside of your domain of control, whether that means

  • internal developers (from the same company), who work for the team across the hall
  • internal developers who work in a different building or different city
  • external partners that work for a business partner

...then it makes sense to insert a management layer in front of those APIs.

As for "utility APIs" - I suppose these would be published by a utility team and then consumed by various developers from numerous other teams inside the company. And in that case, yes, there are benefits to applying API management to such APIs.