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
Alexey Lapitsky
October 25, 2016
Technology
0
80
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
40
Other Decks in Technology
See All in Technology
検証を通して見えてきたTiDBの性能特性
lycorptech_jp
PRO
6
3.3k
シン・Kafka / shin-kafka
oracle4engineer
PRO
7
2.7k
エンタープライズ環境下での Active Directory の運用 TIPS
tamaiyutaro
1
1.6k
コードを書く隙間を見つけて生きていく技術/Findy 思考の現在地
fujiwara3
24
5.1k
ユーザーストーリーのレビューを自動化したみたの
bun913
1
320
スタートアップの技術顧問を3年間続けて発生した事と気付き
biwakonbu
0
160
開発生産性向上サービスを作るFindyが自分たちで開発生産性を爆上げした組織づくりの歩み / Findy's path to boosting its own development productivity 2024-04-17
ma3tk
3
330
日本におけるデータエンジニアリングのこれまでとこれから
foursue
10
2.3k
Signals Unleashed: The Full Guide
rainerhahnekamp
0
370
SREとその組織類型
tatsuo48
8
1.5k
長期間TiDBを使ってきた話 @ 私たちはなぜNewSQLを使うのかTiDB選定5社が語る選定理由と活用LT / Experiences with TiDB Over Time
chibiegg
2
700
Aurora MySQL v3(MySQL8.0互換)の オンラインDDLの罠挙動を全バージョンで検証した
yutakikai
1
150
Featured
See All Featured
Fashionably flexible responsive web design (full day workshop)
malarkey
397
65k
Creatively Recalculating Your Daily Design Routine
revolveconf
209
11k
Mobile First: as difficult as doing things right
swwweet
216
8.6k
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
186
16k
How to train your dragon (web standard)
notwaldorf
72
5.1k
Into the Great Unknown - MozCon
thekraken
10
980
Ruby is Unlike a Banana
tanoku
96
10k
A Modern Web Designer's Workflow
chriscoyier
688
190k
The Language of Interfaces
destraynor
151
23k
Unsuck your backbone
ammeep
662
57k
Debugging Ruby Performance
tmm1
70
11k
How STYLIGHT went responsive
nonsquared
92
4.8k
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?