API Management Strategy

[optimism]

Hello, Dearest Apigee Community,

Before asking this question, I've made a brief mini-research on the "API Management Strategy".

As a result, it seems that ongoing main info could be:

• https://docs.apigee.com/api-platform/fundamentals/api-development-lifecycle
• https://swagger.io/resources/articles/adopting-an-api-first-approach/
• https://cloud.google.com/blog/products/api-management/api-first-digital-transformation

Particularly for me, "API Management Strategy" is the new area of practicing & learning.

From the API Management toolchain perspective, I can see that the following tools are quite helpful:

• Swagger, Spectral - to create & validate Open API Specification (OAS) File
• Apigee - API Management Platform to create API Proxy & other entities (often based on OAS file)
• apigee-deploy-maven-plugin - to deploy API Proxies & others to the Apigee
• Git - to keep track of changes & other SCM, pipeline, DevOps needs
• Postman, Newman - to run manual & pipeline tests of API proxies
• Prism - to mock APIs when needed
• Google's "Cloud Code for Visual Studio Code" with Apigee Emulator for the Local Development
• any other useful tools for API Management?

From the processes standpoint:

• Ensure that valid OAS file provided from the Backend Developers of the given API
• Create API proxies based on the received OAS file
• Create Git repository & setup pipeline with apigee-deploy-maven-plugin, newman & any other appropriate tools 
• Publish APIs on the Apigee Developer Portal
• Continue or repeat steps to have desired results
• any other appropriate process to add?

My question:

Dearest Apigee Community, maybe someone has some general API Management Strategies, that could be shared amongst our community & could be applied in most of the cases?

best regards, 

thanks,

Optimism

[shuhaib_arkn]

Monetization of APIs ,
Developer Portal
Billing