Source: thenewstack.io
Six Signs You’ve Got an API Sprawl Problem
The average enterprise today has over 15,000 APIs in place, https://nonamesecurity.com/api-security-trends-report. Obviously, that’s a few more APIs than the average https://www.nginx.com/resources/glossary/what-is-platform-ops/ team can track in a spreadsheet.
The classic symptom of API sprawl is not knowing what APIs are running across all your environments. This often results from a loose API management policy that allows teams not to register APIs they use only for internal purposes (so-called “shadow APIs”).
Out-of-date API documentation often signals API sprawl is underway, because teams are creating and updating APIs so quickly, they don’t have time to update the docs — or can reasonably claim that.
The classic symptom of API sprawl is not knowing what APIs are running across all your environments. This often results from a loose API management policy that allows teams not to register APIs they use only for internal purposes (so-called “shadow APIs”).
Out-of-date API documentation often signals API sprawl is underway, because teams are creating and updating APIs so quickly, they don’t have time to update the docs — or can reasonably claim that.
Related Articles
Community Partners
DevOps Careers