Enforcing API consistency

The article explores the challenges and solutions associated with maintaining API consistency across teams and organizations. It highlights that while small teams can often resolve API style guide issues through direct interaction, larger organizations face significant friction when multiple teams work on a single or adjacent APIs. The common approach of creating an "API governance team" often leads to delays and resentment, as standards can become rigid and out of touch with real-world needs. Instead, the article advocates for automated checks and tools that help developers maintain consistency without stifling flexibility. It underscores the importance of internal consistency within APIs, cross-organizational consistency, and alignment with domain standards, while also emphasizing the need for flexibility in less critical areas. The article suggests using OpenAPI for automation and automation tools like Spectral and Speakeasy to enforce standards. It also stresses the importance of human judgment in areas like domain alignment and developer experience, recommending processes that combine automation with human review to create a sustainable culture of consistency.