Blog Layout
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.
The 2nd annual code quality report from GitClear found 10x more duplicated code than two years ago and fewer signs of code reuse than ever before.
My feature on InfoWorld explores the state of Kubernetes usability, highlighting various advancements across workload types, support for edge and AI, and new features like observability and security.
It's up to leadership to help prioritize large-scale engineering updates that keep software running smoothly. Kent Wills, Director of Engineering at Yelp, provides insight on the latest DirectorPlus.
Italian for “tapestry,” Arazzo is aptly named since it can be used to weave together sequences of API calls to illustrate a specific business pattern.
I caught up with CTO Itiel Shwartz about leveraging finely tuned models like Komodor’s KlaudiaAI agent for ultra-specific DevOps challenges, like Kubernetes error diagnosis and remediation challenges.
Rolling out AI is all about framing it in a positive light, says GitLab's CTO, Sabrina Farmer. I interviewed her for the latest edition of DirectorPlus for LeadDev, which is out today.
Surmounting risks are encouraging CIOs to future-proof and update their resilience strategies. My latest feature for CIO.com explores resilience head-on.
Today, DX debuted a new developer productivity framework, DX Core 4. Excited to break the news with LeadDev, interviewing one of the designers of the framework.
In this issue of DirectorPlus, Gus Fune shares the story behind reverse engineering a monolithic e-commerce platform following MACH principles, which stands for microservices, APIs, cloud-native, and headless.
Having good API documentation is one thing. Being specification-first is next level. Here are the benefits a specification-driven, git-based approach to documentation can bring to partner API integrations.
