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
540
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
No Assumptions
mitsuhiko
0
54
The Complexity Genie
mitsuhiko
0
86
The Catch in Rye: Seeding Change and Lessons Learned
mitsuhiko
0
270
Runtime Objects in Rust
mitsuhiko
0
340
Rust at Sentry
mitsuhiko
0
390
Overcoming Variable Payloads to Optimize for Performance
mitsuhiko
0
170
Rust API Design Learnings
mitsuhiko
0
500
The Snowball Effect of Open Source
mitsuhiko
0
320
Mobile Games are Living Organisms, Too
mitsuhiko
0
230
Other Decks in Programming
See All in Programming
ソフトウェアエンジニアの成長
masuda220
PRO
12
2k
Better Code Design in PHP
afilina
0
120
『GO』アプリ データ基盤のログ収集システムコスト削減
mot_techtalk
0
130
Writing documentation can be fun with plugin system
okuramasafumi
0
130
Unity Android XR入門
sakutama_11
0
170
React 19アップデートのために必要なこと
uhyo
5
880
Code smarter, not harder - How AI Coding Tools Boost Your Productivity | Angular Meetup Berlin
danielsogl
0
100
PHP ステートレス VS ステートフル 状態管理と並行性 / php-stateless-stateful
ytake
0
110
データベースのオペレーターであるCloudNativePGがStatefulSetを使わない理由に迫る
nnaka2992
0
230
color-scheme: light dark; を完全に理解する
uhyo
7
470
GAEログのコスト削減
mot_techtalk
0
120
SwiftUI Viewの責務分離
elmetal
PRO
2
260
Featured
See All Featured
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.1k
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
49
2.3k
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
114
50k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
656
59k
The Straight Up "How To Draw Better" Workshop
denniskardys
232
140k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
44
7k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
27
1.9k
YesSQL, Process and Tooling at Scale
rocio
172
14k
Code Review Best Practice
trishagee
67
18k
Stop Working from a Prison Cell
hatefulcrawdad
267
20k
Statistics for Hackers
jakevdp
797
220k
The Invisible Side of Design
smashingmag
299
50k
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 :)