TechPrufer
Get started
Spotify
Spotify logoSpotify · Feature trail

Login System Migration

1 post · Dec 2012

What this trail covers

Spotify's login and account management systems have undergone significant evolution, moving from a monolithic 'users' service to a more scalable 'user2' service with a clustered database. This migration involved complex data replication, careful planning of a 56-step rollout, and strategies to minimize downtime and disruption to dependent services. The process highlighted the challenges of scaling legacy systems and the importance of robust migration plans, including handling unexpected delays and resource limitations.

All Spotify trails
  1. Rock the nightThis post details the migration of Spotify's legacy 'users' service to a new 'user2' service. The 'users' service was a scalability bottleneck, handling account creation, login, client settings, and device restrictions. The 'user2' service was introduced with a clustered database to address these limitations. The migration involved a 56-step plan, including pre-migration of data, making the old database read-only, migrating remaining data (which took longer than expected due to overload), and finally switching DNS to direct traffic to the new service. The post also mentions a post-deployment issue with file descriptor limits, which was resolved by increasing the default limit.