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
Shipping Sentry
Search
Armin Ronacher
November 15, 2016
Programming
1
530
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 Catch in Rye: Seeding Change and Lessons Learned
mitsuhiko
0
120
Runtime Objects in Rust
mitsuhiko
0
300
Rust at Sentry
mitsuhiko
0
320
Overcoming Variable Payloads to Optimize for Performance
mitsuhiko
0
130
Rust API Design Learnings
mitsuhiko
0
440
The Snowball Effect of Open Source
mitsuhiko
0
300
Mobile Games are Living Organisms, Too
mitsuhiko
0
200
We gave a Mouse an NDK
mitsuhiko
0
740
Debug is the new Release
mitsuhiko
1
560
Other Decks in Programming
See All in Programming
Assembling the Future: crafting the missing pieces of the Ruby on Wasm puzzle
skryukov
0
120
"Swarming" をコンセプトに掲げるアジャイルチームのベストプラクティス
boykush
1
150
App Router 悲喜交々
quramy
7
370
M5Stackボードの選び方
tanakamasayuki
0
200
タイミーにおけるデータの利用シーンと データ基盤の挑戦
marufeuille
4
3.1k
Делим тесты между QA и разработчиком
mariyasaygina
0
460
Subclassing, Composition, Python, and You
hynek
3
100
CSC509 Lecture 03
javiergs
PRO
0
130
NANIMACHI
naokiito
0
930
フロントエンドの現在地とこれから
koba04
2
980
Applied NLP in the Age of Generative AI
inesmontani
PRO
3
1.1k
ポケモンで考えるコミュニケーション / Communication Lessons from Pokémon
mackey0225
3
130
Featured
See All Featured
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
29
1.7k
Rails Girls Zürich Keynote
gr2m
93
13k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
37
1.7k
[RailsConf 2023] Rails as a piece of cake
palkan
49
4.7k
Java REST API Framework Comparison - PWX 2021
mraible
PRO
28
7.5k
It's Worth the Effort
3n
183
27k
Side Projects
sachag
452
42k
Adopting Sorbet at Scale
ufuk
73
8.9k
Navigating Team Friction
lara
183
14k
Bash Introduction
62gerente
608
210k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
26
2k
The Brand Is Dead. Long Live the Brand.
mthomps
53
38k
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 :)