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
Iterate and Ship
Search
Armin Ronacher
May 10, 2016
Programming
4
400
Iterate and Ship
How we iterate and ship at Sentry.
Armin Ronacher
May 10, 2016
Tweet
Share
More Decks by Armin Ronacher
See All by Armin Ronacher
Runtime Objects in Rust
mitsuhiko
0
280
Rust at Sentry
mitsuhiko
0
290
Overcoming Variable Payloads to Optimize for Performance
mitsuhiko
0
110
Rust API Design Learnings
mitsuhiko
0
430
The Snowball Effect of Open Source
mitsuhiko
0
290
Mobile Games are Living Organisms, Too
mitsuhiko
0
190
We gave a Mouse an NDK
mitsuhiko
0
700
Debug is the new Release
mitsuhiko
1
550
A Future Python
mitsuhiko
0
2.6k
Other Decks in Programming
See All in Programming
ピグパーティにおけるMongoDB CommunityバージョンからAtlasへの移行事例
10969hotaka
0
130
AWS CDKにおける「再利用性」を考える / aws-cdk-reusability
gotok365
6
1.3k
Introduction to GitOps
hwchiu
0
110
コード生成を伴うLLMエージェント - 2024.07.18 Tokyo AI
smiyawaki0820
11
4.1k
企業向け生成AIアプリの 開発から得られた知見
takaakikakei
0
310
しくじり先生 Image Matching Challenge 2024 編
goosehaaan
0
810
Polarsの成長: v0.14からv1.0までの変遷と今後の展望
zerebom
1
350
Mastering Developer Experience: A Roadmap for Success 【開発生産性Conference 2024】
findyinc
1
380
GraphQL はいいぞ! ~Laravel で学ぶ GraphQL 入門~
azuki
1
160
SDCon2024: Enabling DevOps and Team Topologies thru architecture: architecting for fast flow
cer
PRO
0
780
Harnessing Large Language Models for Training-free Video Anomaly Detection
tereka114
1
1.3k
I/O Extended Android in Korea 2024 ~ Whats new in Android development tools
pluu
0
250
Featured
See All Featured
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
26
1.6k
GraphQLの誤解/rethinking-graphql
sonatard
59
9.6k
Automating Front-end Workflow
addyosmani
1362
200k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
78
15k
Agile that works and the tools we love
rasmusluckow
325
20k
GraphQLとの向き合い方2022年版
quramy
36
13k
4 Signs Your Business is Dying
shpigford
178
21k
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
90
47k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
24
1.8k
Web development in the modern age
philhawksworth
203
10k
Rebuilding a faster, lazier Slack
samanthasiow
78
8.5k
5 minutes of I Can Smell Your CMS
philhawksworth
200
19k
Transcript
Armin Ronacher iterate and ship
Armin Ronacher @mitsuhiko Flask / Sentry / Lektor
̿ SENTRY ̀
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
̿ 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)
̿ 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 / npm shrinkwrap
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
̿ 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
̿ 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