Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/2fmEofl.
James Wen tells the story of how Spotify’s infrastructure evolved from teams owning and doting on groups of long-running servers to a distinctive separation of business code and value from the underlying machines all of Spotify's services actually run on. He examines how this evolution also changed the way that Spotify developers write code and the vast increase in iteration and shipping speed. Filmed at qconnewyork.com.
James Wen is currently a Site Reliability Engineer at Spotify. He's on the ALF squad at Spotify, maintaining and developing the tooling for capacity management + provisioning and internal DNS for 150+ teams. He was formerly the Team Lead (Anchor) of the Cloud Foundry Buildpacks team at Pivotal and a core contributor and maintainer of Bundler.