I’ve been enthusiastic about API governance otherwise when working with a number of Go providers.
With one API, retaining conventions constant isn’t too tough. With 10, 20, or extra providers, it turns into a lot tougher.
Totally different groups can regularly introduce their very own approaches to:
- Authentication
- Error responses
- Endpoint naming
- OpenAPI definitions
- API versioning
- Documentation
- Safety necessities
Every little thing can nonetheless work, however the API panorama turns into inconsistent.
I’ve been testing Apidog as an API Governance Device to see whether or not a few of these guidelines could be moved from code evaluations into automated checks.
What I discover helpful is having the ability to mix API growth with:
- Endpoint Compliance Examine
- Documentation Completeness Examine
- Secret Scanner
- RBAC
- Audit Logs
The workflow I’m contemplating for Go providers is:
Go service → OpenAPI → governance checks → API testing → CI/CD
The attention-grabbing half for me is that governance doesn’t essentially have to dam builders. It will probably merely present an early warning when a brand new endpoint doesn’t observe the group’s requirements.
For groups working a number of Go providers:
How do you at present maintain API requirements constant?
Do you employ customized Go tooling, OpenAPI linting, CI guidelines, or a devoted API Governance Device?
And at what level does sustaining your personal governance guidelines grow to be extra work than utilizing a devoted instrument?
