Anatomy of a Schema Drift Incident: 5 Real Patterns That Break Production

Part 2 of 6 in The Silent API Killer series Estimated read time: 12 minutes In Part 1 , I showed you a single API response that silently broke in five different ways after a "minor backend refactor" and how zero tests caught it. I showed you the three lies your API tests tell you every day. I shared numbers from a real audit where 23 out of 47 endpoints had undocumented structural changes while the test suite reported 100% passing for six months straight. That post resonated with a lot of people. The most common response I got? "This literally happened to us last sprint." So if Part 1 was the why should I care, this post is the what exactly am I looking for. Over time, I've noticed that schema drift isn't random. It follows a small number of recurring patterns five, specifically that account for the vast majority of silent API breakages. Each pattern has a distinct root cause, a distinct failure mode, and a distinct reason why conventional testing misses it. Once you learn to recognize