Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Speaker Deck
PRO
Sign in
Sign up for free
Shipping Sentry
Armin Ronacher
November 15, 2016
Programming
1
460
Shipping Sentry
How we ship Sentry to production and on premises.
Armin Ronacher
November 15, 2016
Tweet
Share
More Decks by Armin Ronacher
See All by Armin Ronacher
The Snowball Effect of Open Source
mitsuhiko
0
6
Mobile Games are Living Organisms, Too
mitsuhiko
0
7
We gave a Mouse an NDK
mitsuhiko
0
450
Debug is the new Release
mitsuhiko
1
410
A Future Python
mitsuhiko
0
2.2k
Failing in Rust
mitsuhiko
5
760
A Python for Future Generations
mitsuhiko
19
8.5k
Rust at Sentry
mitsuhiko
4
880
My Python is Rusting
mitsuhiko
2
1.4k
Other Decks in Programming
See All in Programming
Amazon Aurora の v1 が EOL になるので 10 クラスタアップグレードして出てきたノウハウ
dekokun
0
840
Node-RED 3.0 新機能紹介
utaani
0
100
開発速度を5倍早くするVSCodeの拡張機能を作った
purp1eeeee
2
130
Web API連携でCSRF対策がどう実装されてるか調べた / how to implements csrf-detection on Web API
yasuakiomokawa
2
250
Independently together: better developer experience & App performance
bcinarli
0
150
#JJUG_CCC 「サポート」は製品開発? - JDBCライブラリ屋さんが実践する攻めのテクニカルサポートとJavaエンジニアのキャリアについて -
cdataj
0
410
Migrating to Kotlin State & Shared Flows
heyitsmohit
1
180
git on intellij
hiroto_kitamura
0
160
Git・Git-Flowについて
nerusan_main
0
410
パターンマッチングを学んで新しいJavaの世界へ!Java 18までの目玉機能をおさらいしよう / Java 18 pattern matching
ihcomega56
3
370
One does not simply: migrating to Android 12 🤯
oleur
1
120
Overview of The Modern Data Stack / モダンデータスタック概論
satoshihirose
6
3.2k
Featured
See All Featured
Designing Dashboards & Data Visualisations in Web Apps
destraynor
224
49k
Product Roadmaps are Hard
iamctodd
34
6.5k
Bootstrapping a Software Product
garrettdimon
296
110k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
104
16k
Fontdeck: Realign not Redesign
paulrobertlloyd
73
4.1k
Build The Right Thing And Hit Your Dates
maggiecrowley
19
1.2k
The Cult of Friendly URLs
andyhume
68
4.8k
Atom: Resistance is Futile
akmur
255
20k
Imperfection Machines: The Place of Print at Facebook
scottboms
253
12k
Three Pipe Problems
jasonvnalue
89
8.7k
Docker and Python
trallard
27
1.6k
Building Adaptive Systems
keathley
25
1.1k
Transcript
Armin Ronacher Shipping Sentry
Armin Ronacher @mitsuhiko Flask / Sentry / Lektor
Find the Slides at lucumr.pocoo.org/talks
reach out to me! I want to talk :)
sentry.io
None
None
None
None
None
「 THE TWO PRODUCTS 」
sentry vs ‘getsentry’
sentry open source repo on-premise monthly releases
‘getsentry’ billing & quotas depends on sentry hourly deploys
「 GROWING THE TEAM 」
2.5 to 25 more process keep processes light keep developers
happy
2 locations process in code natural for us because of
the Open Source nature
「 THE GOALS 」
deploy in seconds be unable to screw up and if
you do: instant rollbacks
tag a release once a month
「 WORKFLOW 」
commit review integration deploy
requires good test coverage requires good local setup makes it
easier for newcomers
「 COMMITTING 」
lint on commit!
1 Release / Month 5 Deployments / Day On Prem:
Hosted:
None
master is stable
1. branch off master 2. pull request 3. merge
all the pull requests
!! AVOID DOWNTIME !!
postgres <3 transactional ddl, concurrent indexes, cheap alter table add
nullable columns
bidirectional compatibility
separation of state and connections
「 CONTINUOUS TESTING 」
sentry travis-ci.org test all the code
‘getsentry’ travis-ci.com test code relevant for us
「 CONTINUOUS DELIVERY 」
FREIGHT wait for travis > build > ship
bidirectional communication with the main slack channel
dev never matches prod :(
thus: fast rollbacks! (backwards + forwards compatibility)
「 CODE STRUCTURE 」
large systems are organisms
not all things will run the same code at the
same time
data schema ~ code behavior
break up larger features
feature flag it! (we shipped some code to on-prem we
backed out)
「 REPO STRUCTURE 」
move towards “monorepos” (but within what is possible with our
tools) {not as mono as we would like}
「 MOVING PARTS 」
keep dev basic: fewer parts
do not diverge dev from prod too much
virtual machines and docker are not an acceptable dev environment
「 REPRODUCIBLE BUILDS 」
pip freeze / yarn
nothing is more frustrating than a failed deploy because a
dependency of a dependency of a dependency of a dependency pushed out a broken release
build once > ship to many
「 BINARY DEPS 」
OS X & “manylinux”
C/C++/Rust Modules for Python
Build in Docker on old CentOS
Debian / RHEL / Ubuntu
「 MONITOR FAILURES 」
associate failures to users
map support requests to failures
use sentry :-)
「 FRIENDLY ROBOTS 」
replace yourself!
bots and webhooks
github hooks
notify to communication hub
testing danger.systems
「 BETTER CLIMATE 」
the more robots, the better the integration, the smaller the
fear of doing damage
If you can launch a feature on your first day
of work that's motivating
also: happy customers
Q&A reach out to me! I want to talk :)