Slide 1

Slide 1 text

Armin Ronacher Shipping Sentry

Slide 2

Slide 2 text

Armin Ronacher @mitsuhiko Flask / Sentry / Lektor

Slide 3

Slide 3 text

Find the Slides at lucumr.pocoo.org/talks

Slide 4

Slide 4 text

reach out to me! I want to talk :)

Slide 5

Slide 5 text

sentry.io

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

「 THE TWO PRODUCTS 」

Slide 12

Slide 12 text

sentry vs ‘getsentry’

Slide 13

Slide 13 text

sentry open source repo on-premise monthly releases

Slide 14

Slide 14 text

‘getsentry’ billing & quotas depends on sentry hourly deploys

Slide 15

Slide 15 text

「 GROWING THE TEAM 」

Slide 16

Slide 16 text

2.5 to 25 more process keep processes light keep developers happy

Slide 17

Slide 17 text

2 locations process in code natural for us because of the Open Source nature

Slide 18

Slide 18 text

「 THE GOALS 」

Slide 19

Slide 19 text

deploy in seconds be unable to screw up and if you do: instant rollbacks

Slide 20

Slide 20 text

tag a release once a month

Slide 21

Slide 21 text

「 WORKFLOW 」

Slide 22

Slide 22 text

commit review integration deploy

Slide 23

Slide 23 text

requires good test coverage requires good local setup makes it easier for newcomers

Slide 24

Slide 24 text

「 COMMITTING 」

Slide 25

Slide 25 text

lint on commit!

Slide 26

Slide 26 text

1 Release / Month 5 Deployments / Day On Prem: Hosted:

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

master is stable

Slide 29

Slide 29 text

1. branch off master 2. pull request 3. merge

Slide 30

Slide 30 text

all the pull requests

Slide 31

Slide 31 text

!! AVOID DOWNTIME !!

Slide 32

Slide 32 text

postgres <3 transactional ddl, concurrent indexes, cheap alter table add nullable columns

Slide 33

Slide 33 text

bidirectional compatibility

Slide 34

Slide 34 text

separation of state and connections

Slide 35

Slide 35 text

「 CONTINUOUS TESTING 」

Slide 36

Slide 36 text

sentry travis-ci.org test all the code

Slide 37

Slide 37 text

‘getsentry’ travis-ci.com test code relevant for us

Slide 38

Slide 38 text

「 CONTINUOUS DELIVERY 」

Slide 39

Slide 39 text

FREIGHT wait for travis > build > ship

Slide 40

Slide 40 text

bidirectional communication with the main slack channel

Slide 41

Slide 41 text

dev never matches prod :(

Slide 42

Slide 42 text

thus: fast rollbacks! (backwards + forwards compatibility)

Slide 43

Slide 43 text

「 CODE STRUCTURE 」

Slide 44

Slide 44 text

large systems are organisms

Slide 45

Slide 45 text

not all things will run the same code at the same time

Slide 46

Slide 46 text

data schema ~ code behavior

Slide 47

Slide 47 text

break up larger features

Slide 48

Slide 48 text

feature flag it! (we shipped some code to on-prem we backed out)

Slide 49

Slide 49 text

「 REPO STRUCTURE 」

Slide 50

Slide 50 text

move towards “monorepos” (but within what is possible with our tools) {not as mono as we would like}

Slide 51

Slide 51 text

「 MOVING PARTS 」

Slide 52

Slide 52 text

keep dev basic: fewer parts

Slide 53

Slide 53 text

do not diverge dev from prod too much

Slide 54

Slide 54 text

virtual machines and docker are not an acceptable dev environment

Slide 55

Slide 55 text

「 REPRODUCIBLE BUILDS 」

Slide 56

Slide 56 text

pip freeze / yarn

Slide 57

Slide 57 text

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

Slide 58

Slide 58 text

build once > ship to many

Slide 59

Slide 59 text

「 BINARY DEPS 」

Slide 60

Slide 60 text

OS X & “manylinux”

Slide 61

Slide 61 text

C/C++/Rust Modules for Python

Slide 62

Slide 62 text

Build in Docker on old CentOS

Slide 63

Slide 63 text

Debian / RHEL / Ubuntu

Slide 64

Slide 64 text

「 MONITOR FAILURES 」

Slide 65

Slide 65 text

associate failures to users

Slide 66

Slide 66 text

map support requests to failures

Slide 67

Slide 67 text

use sentry :-)

Slide 68

Slide 68 text

「 FRIENDLY ROBOTS 」

Slide 69

Slide 69 text

replace yourself!

Slide 70

Slide 70 text

bots and webhooks

Slide 71

Slide 71 text

github hooks

Slide 72

Slide 72 text

notify to communication hub

Slide 73

Slide 73 text

testing danger.systems

Slide 74

Slide 74 text

「 BETTER CLIMATE 」

Slide 75

Slide 75 text

the more robots, the better the integration, the smaller the fear of doing damage

Slide 76

Slide 76 text

If you can launch a feature on your first day of work that's motivating

Slide 77

Slide 77 text

also: happy customers

Slide 78

Slide 78 text

Q&A reach out to me! I want to talk :)