Why does my live API contract only break in ways my CI pipeline cannot see?
机会
Consumer-driven contract testing catches breaking changes before merge, but it pins contracts at PR time and has no mechanism to detect semantic drift that accumulates in a live service after deployment. Teams add undocumented fields in production hotfixes, change error shapes to unblock an incident, or relax validation without touching the OpenAPI spec. The World Quality Report 2025 names undetected API schema drift a top-three cause of production incidents in distributed systems, and estimates roughly 70 percent of API failures in production passed all CI checks. No current tool continuously monitors real production traffic against a published contract and surfaces violations as they accumulate rather than at merge time.
为什么重要
Watching actual live traffic against the contract you published would close the last mile between what your API promises and what it silently stopped delivering.
我如何评估机会
机会评分是我的个人判断，而非量化指标：痛苦程度、发生频率，以及当前解决方案的匮乏程度。分数越高，意味着我认为越值得去构建。
出现时造成的痛苦程度。
人们实际遇到它的频率。
当前针对它的优质工具有多匮乏。