CANARY IN THE INTERNET MINE WHO IS THIS TALK FOR? FOLKS WHO: make - - PowerPoint PPT Presentation

canary in the internet mine
SMART_READER_LITE
LIVE PREVIEW

CANARY IN THE INTERNET MINE WHO IS THIS TALK FOR? FOLKS WHO: make - - PowerPoint PPT Presentation

BROOK SHELLEY CANARY IN THE INTERNET MINE WHO IS THIS TALK FOR? FOLKS WHO: make applications or websites that you visit in a browser. launch a new versions - even a minor one. need to respond to a downtime page. ever make


slide-1
SLIDE 1

CANARY IN THE INTERNET MINE

BROOK SHELLEY

slide-2
SLIDE 2

WHO IS THIS TALK FOR?

FOLKS WHO:

▸ make applications or websites that you visit in a browser. ▸ launch a new versions - even a minor one. ▸ need to respond to a downtime page. ▸ ever make mistakes.

THIS IS FOR YOU

slide-3
SLIDE 3

EVERYONE SHOULD BE ABLE TO RELEASE CODE.

If a dev deploys code on your infrastructure, 
 but no one can see it, does it matter?

slide-4
SLIDE 4

IT’S COOL, THERE’S A CHANGELOG

brook (me)

TEXT

slide-5
SLIDE 5

CANARY? YES, PLEASE.

*Please note no birds were harmed while writing this talk

slide-6
SLIDE 6

TERMS

▸ Blue/Green: ▸ two production environments as identical as possible.

usually, only one is live at a time.

▸ Canary: ▸ testing term originally referring to live canaries used to

check for dangerous gasses in mines.

▸ in tech: server/service/deploy dies, there’s problems.

slide-7
SLIDE 7

CANARY

▸ A small portion of live traffic. ▸ Testing in production. ▸ If the release dies, abandon that route.

😱😱😱

slide-8
SLIDE 8

CURRENT STATE

▸ Your app is a monolith or maybe microservicces ▸ QA & Testing are expensive. ▸ Things still break. ▸ Rolling back your code takes ⏱ & costs 💱.

slide-9
SLIDE 9

99 SERVICES, 99 PROBLEMS?

▸ Each service or endpoint runs as a microservice. ▸ Incremental release of your application is possible. ▸ Combine with canary releases for success. ▸ Release or roll back service by service.

slide-10
SLIDE 10

MONITOR

▸ Early. ▸ Often. ▸ Customer focused metrics.

slide-11
SLIDE 11

INDIVIDUAL SERVICES

▸ Per-endpoint/per-service testing. ▸ Measure often - metrics. ▸ Take immediate action. ▸ Stop ruining weekends.

slide-12
SLIDE 12

HOW DO WE GET THERE? IT SOUNDS HARD.

slide-13
SLIDE 13

PROXIES & ROUTING.

slide-14
SLIDE 14

Blue/Green Releases

slide-15
SLIDE 15

DEMO TIME.

slide-16
SLIDE 16

WRAP-UP

▸ Per-endpoint/per-service releasing. ▸ Measure often with user-centric metrics. ▸ Routing makes roll-back easy and quick. ▸ Stop ruining weekends. ▸ Developers triage at their leisure.

slide-17
SLIDE 17

THANKS!

@brookshelley

brook@turbinelabs.io