Spotify and Python: love at first sight
summary
Spotify describes a concrete backend: many tiny services (about 60) talking HTTP/Thrift with a custom open client protocol, an access point handles authentication and multiplexing, search uses Java Lucene, playlist logic becomes a distributed VCS and is being reimplemented in Java/Scala, core storage uses PostgreSQL plus Cassandra since spring, fast lookups use Tokyo Cabinet and memcache, Hadoop ingests logs, deployment uses Git, 428 repos, Puppet and 10m packages, and the stack moves from Twisted then gevent to scale for 10 million users and 1 million paying.
AI-written summary · about
chapters (23)
- 0:00intro
- 0:30why am I here
- 2:08Running water or electricity
- 2:36Native desktop client
- 3:31Spotify box
- 4:24Spotify staff
- 5:24Windows client
- 7:54Twisted
- 8:21Square Root
- 8:39Architecture
- 14:07Core Services
- 15:53Tools
- 16:37Service
- 17:27Frameworks
- 18:07Languages
- 18:27Services
- 19:22Protocols
- 20:45Storage
- 22:18Cassandra
- 24:01Adam
- 25:22Deployment
- 27:30Future problems
- 27:52Thank you
related talks
33mLessons learned building Python microservices
35mDiversity and Data: Cases in the Music Industry
21mWhen R Met Python: A Meet Cute on Posit Connect
44mPython in the MicroServices world
26mBuilding A Python Service Using Open Source Components That Connect, Transform & Deliver Data In RT
19mPython for Cloud Services and Infrastructure Management
40mPython microservices on PaaS done right
26mPython as a Universal Backend
