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
I'm working with Zuplo on some new content around their MCP Gateway release. First up: a deep comparison of MCP gateways on the market!
The constant barrage of AI layoffs is overshadowing the economic reasons behind these cuts, as well as the net-positive talent redistribution happening at large.
My latest for InfoWorld reviews MCP servers and agent-ready tools for connecting AI agents with popular database styles.
For my latest DirectorPlus edition, Joel Carusone from NinjaOne shares how engineering leaders can build the muscle for making tough calls.
My latest InfoWorld feature explores how Model Context Protocol (MCP) supports context engineering for AI-assisted coding.
My latest for Nordic APIs explores 10 API key security risks and what to use alongside keys for stronger API security.
The yearly API conference, apidays New York, is a hotbed for solid discussion on what's top of mind in the API space, and as MC I had a front row seat.
My latest for CIO Online features real results form CIOs actively deploying AI agents to empower sales and revenue teams.
Reports say consumers are souring on AI everywhere, all the time. So, at the risk of losing trust, or even potential business, is adding AI to an existing product really worth it?
Cloudflare rebuilt Next.js over a weekend using agentic coding.
