Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Spotify's journey to GCP
Search
Sponsored
·
SiteGround - Reliable hosting with speed, security, and support you can count on.
→
Alexey Lapitsky
October 25, 2016
Technology
0
85
Spotify's journey to GCP
Alexey Lapitsky
October 25, 2016
Tweet
Share
More Decks by Alexey Lapitsky
See All by Alexey Lapitsky
Perimeter Management at Spotify
vzctl
0
44
Other Decks in Technology
See All in Technology
Contract One Engineering Unit 紹介資料
sansan33
PRO
0
13k
SRE Enabling戦記 - 急成長する組織にSREを浸透させる戦いの歴史
markie1009
0
140
日本の85%が使う公共SaaSは、どう育ったのか
taketakekaho
1
230
30万人の同時アクセスに耐えたい!新サービスの盤石なリリースを支える負荷試験 / SRE Kaigi 2026
genda
4
1.3k
OWASP Top 10:2025 リリースと 少しの日本語化にまつわる裏話
okdt
PRO
3
830
AzureでのIaC - Bicep? Terraform? それ早く言ってよ会議
torumakabe
1
590
AI駆動開発を事業のコアに置く
tasukuonizawa
1
320
【Oracle Cloud ウェビナー】[Oracle AI Database + AWS] Oracle Database@AWSで広がるクラウドの新たな選択肢とAI時代のデータ戦略
oracle4engineer
PRO
2
180
Tebiki Engineering Team Deck
tebiki
0
24k
Codex 5.3 と Opus 4.6 にコーポレートサイトを作らせてみた / Codex 5.3 vs Opus 4.6
ama_ch
0
190
Introduction to Sansan for Engineers / エンジニア向け会社紹介
sansan33
PRO
6
68k
M&A 後の統合をどう進めるか ─ ナレッジワーク × Poetics が実践した組織とシステムの融合
kworkdev
PRO
1
480
Featured
See All Featured
Bash Introduction
62gerente
615
210k
Building Adaptive Systems
keathley
44
2.9k
How to Ace a Technical Interview
jacobian
281
24k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
287
14k
Gemini Prompt Engineering: Practical Techniques for Tangible AI Outcomes
mfonobong
2
280
Build your cross-platform service in a week with App Engine
jlugia
234
18k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
122
21k
Six Lessons from altMBA
skipperchong
29
4.2k
Optimising Largest Contentful Paint
csswizardry
37
3.6k
Building Experiences: Design Systems, User Experience, and Full Site Editing
marktimemedia
0
410
A Modern Web Designer's Workflow
chriscoyier
698
190k
Discover your Explorer Soul
emna__ayadi
2
1.1k
Transcript
Spotify’s journey to GCP
~# whoami Alexey Lapitsky / @vzctl
[email protected]
Site Reliability Engineer
@Spotify PM for the service track of the GCP migration
Agenda • History • Why GCP? • The biggest mistake
• Learnings • Questions!
Spotify’s cloud history 2010 Manual VM provisioning 2012 Cloudstack, reached
~700 instances 2013 Amazon EC2 2015 Google Cloud Platform
Current status • 4 data centers, ~10k physical servers •
Micro-service architecture, ~1k different services • Mostly commodity hardware (Dell) • Fully automated, self-service server provisioning Moving everything to GCP
Focus
Why GCP?
Why GCP? • BigData • Culture • Timing • Partnership
Our worst mistake
Spoticloud CLI REST DB Cloudstack AWS Puppet DNS Server •
CLI Tool + REST Server • User authentication with ssh agent: github.com/spotify/crtauth SSH Jumphost
Looks awesome! • No need to distribute AWS accounts •
No need to manage ACLs • Extremely easy to use ~# spcloud create --name web --project alexey
… or not really :( • Testing environment, shamelessly misused
for production • No accountability or a proper ownership tracking ◦ 60% of instances were wasting money • Access only to the basic cloud primitives ◦ Which are already available on-premise Currently being deprecated.
GCP Migration
Cross-project networking (XPN)
None
Things we learned • VPN is tricky • GCP network
is great • Keep an eye on quotas • Live VM migration! • Think about ACL mgmt in advance • BigTable, GCS, BigQuery are awesome
Questions?