Community highlight for a presentation on Azure API Management service using APIOps including best practices and patterns for source control, CI/CD, and other concerns.
I was fortunate to present to the Wellington .Net User Group about my experience using the Azure API Management (APIM) service. In the presentation I cover some of the aspects that I often see teams re-invent solutions, and in my opinion, misuse Azure APIM.
Mastering Azure API Management - Demos and Best practices
Why am I highlighting this again?
All aspects of a solution should be under source control to ensure consistency, collaboration, and reliability. Azure APIM is not an exception. APIOps, or Azure API Management (APIM) with DevOps, is a DevOps approach for managing APIs in Azure API Management (APIM). The focus of APIOps is on automation, CI/CD, and version control for APIs.
The guidance here is adopt a strategy for APIM as early as possible as well as don't reinvent. APIOps is a flexible, open source project with an active and engaged community. Most of the organizations I work with have either wrote their own solution or have gone without putting APIM under versioned source control with automated CI/CD. The main reason for this is the team have not allowed themselves the time to learn and adopt APIOps.
So take the time to fully evaluate APIOps before rolling your own and never go without.
Here are some references to help you get started:
- This page in the wiki gives you an idea of the content and structure of how the resources are saved to files.
- Spend the time to read and watch the video on the GitHub readme as a good starting point
And, like always, let me know if you agree or disagree by commenting below.
Cheers!
