Business

Spotify Doubles Monthly Code Changes with AI Agents

Spotify more than doubled its monthly merged code changes to 17,000 using AI, forcing the streaming giant to revamp its testing and safeguards as software output outpaces verification controls.

InfoQ AI22 hrs agoBusiness
Image: InfoQ AI

Development volume at Spotify expanded dramatically after incorporating AI into its workflow, pushing monthly merged code changes from roughly 8,100 to 17,000 year over year in August. The surge tests an architecture supporting nearly 3,000 production services, 777 million monthly active users, around 100 million concurrent clients, and 11 to 12 million backend requests per second. To maintain reliability, the audio giant is updating its monitoring, rollout safeguards, capacity planning, and rollback capabilities.

Key automation tools drive this accelerated throughput. Spotify's Fleet Management system has merged over 2.5 million automated maintenance pull requests. To manage complex tasks, the platform uses Honk, a background coding agent that runs Claude via the Agent SDK inside Kubernetes pods, alongside Fleetshift for scheduling and orchestration. Using this setup, Spotify recently executed a backend Java migration across its infrastructure in just three days. Consequently, quality and optimization tasks grew from 27% to 31% of merged changes, while maintenance and configuration dropped from 31% to 25%.

However, increased volume has strained existing verification systems. On June 24, a content processing pipeline handling over 500,000 daily uploads suffered a 10% throughput drop due to a scheduling bug, delaying episode publishing from minutes to hours. An automated dependency upgrade also passed checks before failing in production. Spotify noted that while AI-authored code caused no material direct increase in rework, total change volume ran ahead of some quality controls.

These results reflect findings from Google's 2025 DORA research, which connected AI adoption to higher software delivery throughput alongside reduced delivery stability. For engineering teams, Spotify's experience demonstrates that while automated tools simplify writing code, robust automated testing, rapid feedback loops, and schedule-aware rollouts are essential to handle high-velocity delivery.

This is our own summary of reporting by InfoQ AI

More in Business