Designing the Spotify perimeter

This post details the initial design and implementation of Spotify's network perimeter, focusing on web load balancers and proxy systems. It describes the transition from a chaotic, unmanaged network to a structured perimeter with self-service capabilities for developers. Key technical details include the use of dyn.com for DNS failover, nginx for web load balancing (with HAProxy for active health checks), and Puppet for configuration management. It also touches on multi-tenancy for different traffic types (websites, APIs, payments) and the security implications of exposing services.