As a Go challenge grows, preserving API conventions constant throughout companies can change into surprisingly tough.
One service may use one error format, one other may deal with pagination otherwise, and a 3rd may expose barely completely different naming conventions.
I’m questioning how different Go groups deal with this sort of API governance.
For instance, do you robotically verify issues like:
- OpenAPI validity
- Endpoint naming conventions
- HTTP standing code utilization
- Authentication necessities
- Required documentation
- Breaking API adjustments
- Constant error responses
- Deprecated endpoints
I’m particularly involved in automated checks that may run as a part of CI moderately than relying totally on code overview.
For a group with a number of Go companies, I’m imagining one thing like:
OpenAPI → governance checks → assessments → overview → deployment
Do you employ an current API governance software, OpenAPI linters, customized Go tooling, or GitHub Actions to implement these guidelines?
What checks have really been helpful in your expertise, and which of them created an excessive amount of friction?
