5 ways to test APIs for breaking changes
Bill Doerrfeld | August 1, 2024
No developer likes an API that breaks. Breaking changes are changes made to APIs that cause some kind of disruption on the integration side.
Thankfully, there are ways you can test for breaking changes in APIs, using methods like specification-based diffing, contract testing, functional testing, performance monitoring, following developer-centric communications, and other tactics.
I recently wrote up a summary of various methods and tools for testing APIs for breaking changes on the
Treblle blog. Give it a read
here! I especially enjoyed using oasdiff to compare OpenAPI Specification definitions — that tool is awesome.
Other Blog Posts
My InfoWorld feature reviews the key building blocks in agentic systems and with real-world examples from Shopify, Block, and others.
My latest InfoWorld feature explores what makes an enterprise MCP registry effective, from semantic discovery to governance and security for AI agents.
My first-ever contribution to CSO Online looks at the shifting landscape, from perimeter-based security to API security, and how CISOs are responding.
My latest feature for The New Stack looks into solutions being proposed to fix open source Slopmageddon.
My latest DirectorPlus looks at how agentic AI is reshaping platform engineering at Squarespace: less shared code and more developer experience focus.
Usage-based pricing is reshaping the API economy. Discover 5 API monetization success stories, including OpenAI, Plaid, and AssemblyAI.
Why event-driven APIs matter for AI workflows, enabling real-time data, scalable systems, and responsive agent behavior.
While hardware usually gets the spotlight in physical AI, the real differentiator won't be hardware. It'll be the models.
In the latest DirectorPlus, Workato's CTO explains how MCP-enabled integration catalyzed internal AI usage and ROI.
My latest on InfoWorld reviews MCP servers from 5 major cloud providers
