×
Copy
Open
Link
Embed
Share
Beginning
This slide
Copy link URL
Copy link URL
Copy iframe embed code
Copy iframe embed code
Copy javascript embed code
Copy javascript embed code
Share
Tweet
Share
Tweet
Slide 1
Slide 1 text
BUILDING RESILIENT FRONTEND SYSTEMS Ian Feather - BuzzFeed - @ianfeather
Slide 2
Slide 2 text
No content
Slide 3
Slide 3 text
RESILIENCE IS FUNCTION IN A HOSTILE ENVIRONMENT
Slide 4
Slide 4 text
UNDERSTAND YOUR TIERS OF USER EXPERIENCE
Slide 5
Slide 5 text
GUARANTEE THE MOST BASIC LEVEL OF UX
Slide 6
Slide 6 text
1. HOW OUR SYSTEMS FAIL 2. DESIGNING FOR FAILURE 3. MITIGATING RISK 4. LEARNING FROM FAILURE
Slide 7
Slide 7 text
HOW OUR SYSTEMS FAIL SECTION 1
Slide 8
Slide 8 text
HOW OUR SYSTEMS FAIL 1. MALICIOUS INTERFERENCE
Slide 9
Slide 9 text
HTTPS IS TABLE STAKES
Slide 10
Slide 10 text
HTTPS IS TABLE STAKES
Slide 11
Slide 11 text
HOW OUR SYSTEMS FAIL 1. MALICIOUS INTERFERENCE
Slide 12
Slide 12 text
HOW OUR SYSTEMS FAIL 1. MALICIOUS INTERFERENCE 2. 3RD PARTY AVAILABILITY
Slide 13
Slide 13 text
CONTROL YOUR POINTS OF FAILURE
Slide 14
Slide 14 text
2016
Slide 15
Slide 15 text
2016 DYN DNS 5 HRS
Slide 16
Slide 16 text
2016 DYN DNS 5 HRS AWS s3 9 HRS 2017
Slide 17
Slide 17 text
2016 DYN DNS 5 HRS AWS s3 9 HRS 2017 Fastly CDN 1 HR
Slide 18
Slide 18 text
2016 DYN DNS 5 HRS AWS s3 9 HRS 2017 Fastly CDN 1 HR AWS S3 2 hrs
Slide 19
Slide 19 text
HOW OUR SYSTEMS FAIL 1. MALICIOUS INTERFERENCE 2. 3RD PARTY AVAILABILITY
Slide 20
Slide 20 text
HOW OUR SYSTEMS FAIL 1. MALICIOUS INTERFERENCE 2. 3RD PARTY AVAILABILITY 3. DEVELOPER ERROR
Slide 21
Slide 21 text
ADD SLIDE ABOUT SENTRY
Slide 22
Slide 22 text
SLACK ALERTS
Slide 23
Slide 23 text
KNOWING IT’S BROKEN BEFORE TWITTER DOES
Slide 24
Slide 24 text
THEORY VS PRACTICE
Slide 25
Slide 25 text
HOW OUR SYSTEMS FAIL 1. MALICIOUS INTERFERENCE 2. 3RD PARTY AVAILABILITY 3. DEVELOPER ERROR
Slide 26
Slide 26 text
HOW OUR SYSTEMS FAIL 1. MALICIOUS INTERFERENCE 2. 3RD PARTY AVAILABILITY 3. DEVELOPER ERROR 4. THE NETWORK
Slide 27
Slide 27 text
THEORY VS PRACTICE
Slide 28
Slide 28 text
THEORY VS PRACTICE
Slide 29
Slide 29 text
~1% OF REQUESTS FOR JAVASCRIPT WILL TIMEOUT
Slide 30
Slide 30 text
13 MILLION REQUESTS FOR JAVASCRIPT WILL TIMEOUT
Slide 31
Slide 31 text
HOW OUR SYSTEMS FAIL 1. MALICIOUS INTERFERENCE 2. 3RD PARTY AVAILABILITY 3. DEVELOPER ERROR 4. THE NETWORK
Slide 32
Slide 32 text
HOW OUR SYSTEMS FAIL 1. MALICIOUS INTERFERENCE 2. 3RD PARTY AVAILABILITY 3. DEVELOPER ERROR 4. THE NETWORK 5. USER’S PRIVILEGE
Slide 33
Slide 33 text
~9% OF OUR USERS USE SOME FORM OF CONTENT BLOCKER
Slide 34
Slide 34 text
~4% WON’T SUCCESSFULLY DOWNLOAD OUR FONTS
Slide 35
Slide 35 text
40 MILLION PAGEVIEWS PER MONTH
Slide 36
Slide 36 text
HOW OUR SYSTEMS FAIL 1. MALICIOUS INTERFERENCE 2. 3RD PARTY AVAILABILITY 3. DEVELOPER ERROR 4. THE NETWORK 5. USER’S PRIVILEGE
Slide 37
Slide 37 text
HOPE FOR THE BEST?
Slide 38
Slide 38 text
DESIGN FOR FAILURE SECTION 2
Slide 39
Slide 39 text
DESIGN FOR FAILURE 1. PRIORITIZE CRITICAL PARTS OF THE PAGE
Slide 40
Slide 40 text
User FONTS html IMAGES DATA (xhr) IMAGES CSS JS IMAGES
Slide 41
Slide 41 text
User FONTS html IMAGES DATA (xhr) IMAGES CSS JS IMAGES Images
Slide 42
Slide 42 text
User FONTS html IMAGES DATA (xhr) IMAGES CSS JS IMAGES HTML
Slide 43
Slide 43 text
No content
Slide 44
Slide 44 text
No content
Slide 45
Slide 45 text
No content
Slide 46
Slide 46 text
DESIGN FOR FAILURE 1. PRIORITIZE CRITICAL PARTS OF THE PAGE
Slide 47
Slide 47 text
DESIGN FOR FAILURE 1. PRIORITIZE CRITICAL PARTS OF THE PAGE 2. MAKE ERRORS A FIRST CLASS CITIZEN
Slide 48
Slide 48 text
SOMETHING BROKE! SHOULD I TELL THEM?
Slide 49
Slide 49 text
No content
Slide 50
Slide 50 text
✘
Slide 51
Slide 51 text
✘
Slide 52
Slide 52 text
IT BROKE. SHOULD I TELL THEM?
Slide 53
Slide 53 text
No content
Slide 54
Slide 54 text
DESIGN FOR FAILURE 1. PRIORITIZE CRITICAL PARTS OF THE PAGE 2. MAKE ERRORS A FIRST CLASS CITIZEN
Slide 55
Slide 55 text
MITIGATE RISK SECTION 3
Slide 56
Slide 56 text
MITIGATE RISK 1. LOCK YOUR RUNTIME DEPENDENCIES
Slide 57
Slide 57 text
CONTROL YOUR POINTS OF FAILURE
Slide 58
Slide 58 text
No content
Slide 59
Slide 59 text
MITIGATE RISK 1. LOCK YOUR RUNTIME DEPENDENCIES
Slide 60
Slide 60 text
MITIGATE RISK 1. LOCK YOUR RUNTIME DEPENDENCIES 2. BUILD IN REDUNDANCY
Slide 61
Slide 61 text
HAVE TWO OF EVERYTHING
Slide 62
Slide 62 text
Asset SERVER 1
Slide 63
Slide 63 text
Asset SERVER 1 www.asset-server-one.com/styles.css
Slide 64
Slide 64 text
Asset SERVER 1 www.asset-server-one.com/styles.css
Slide 65
Slide 65 text
✖ Asset SERVER 1 www.asset-server-one.com/styles.css
Slide 66
Slide 66 text
✖ Asset SERVER 1 Asset SERVER 2 www.asset-server-one.com/styles.css
Slide 67
Slide 67 text
✖ Asset SERVER 1 Asset SERVER 2 www.asset-server-two.com/styles.css www.asset-server-one.com/styles.css
Slide 68
Slide 68 text
✖ Asset SERVER 1 Asset SERVER 2 www.asset-server-two.com/styles.css www.asset-server-one.com/styles.css
Slide 69
Slide 69 text
Asset SERVER 1 Asset SERVER 2 Proxy service
Slide 70
Slide 70 text
Asset SERVER 1 Asset SERVER 2 www.asset-server.com/styles.css Proxy service
Slide 71
Slide 71 text
Asset SERVER 1 Asset SERVER 2 www.asset-server.com/styles.css Proxy service
Slide 72
Slide 72 text
Asset SERVER 1 Asset SERVER 2 www.asset-server.com/styles.css Proxy service
Slide 73
Slide 73 text
PLAN Z
Slide 74
Slide 74 text
MITIGATE RISK 1. LOCK YOUR RUNTIME DEPENDENCIES 2. BUILD IN REDUNDANCY
Slide 75
Slide 75 text
MITIGATE RISK 1. LOCK YOUR RUNTIME DEPENDENCIES 2. BUILD IN REDUNDANCY 3. SERVE STALE CONTENT
Slide 76
Slide 76 text
SERVER
Slide 77
Slide 77 text
SERVER CDN
Slide 78
Slide 78 text
SERVER CDN
Slide 79
Slide 79 text
SERVER CDN
Slide 80
Slide 80 text
SERVER CDN
Slide 81
Slide 81 text
SERVER CDN
Slide 82
Slide 82 text
SERVER CDN
Slide 83
Slide 83 text
CDN SERVER
Slide 84
Slide 84 text
CDN ✖ SERVER
Slide 85
Slide 85 text
CDN ✖ SERVICE WORKER SERVER
Slide 86
Slide 86 text
CDN ✖ SERVICE WORKER SERVER
Slide 87
Slide 87 text
MITIGATE RISK 1. LOCK YOUR RUNTIME DEPENDENCIES 2. BUILD IN REDUNDANCY 3. SERVE STALE CONTENT
Slide 88
Slide 88 text
LEARN FROM MISTAKES SECTION 4
Slide 89
Slide 89 text
LEARN FROM MISTAKES 1. POSTMORTEMS
Slide 90
Slide 90 text
BLAMELESS
Slide 91
Slide 91 text
HOW DID WE HANDLE IT AS A TEAM?
Slide 92
Slide 92 text
HOW COULD IT HAVE BEEN PREVENTED?
Slide 93
Slide 93 text
LEARN FROM MISTAKES 1. POSTMORTEMS
Slide 94
Slide 94 text
LEARN FROM MISTAKES 1. POSTMORTEMS 2. FIRE DRILLS & CHAOS TESTING
Slide 95
Slide 95 text
FIRE DRILLS ARE A SAFE SPACE TO PRACTICE
Slide 96
Slide 96 text
1. LIMIT IMPACT 2. BE DECISIVE 3. DELEGATE EARLY
Slide 97
Slide 97 text
CHAOS TESTING
Slide 98
Slide 98 text
DELIBERATELY INTRODUCE FAILURE TO ENSURE YOUR SYSTEMS ARE RESILIENT
Slide 99
Slide 99 text
LEARN FROM MISTAKES 1. POSTMORTEMS 2. FIRE DRILLS & CHAOS TESTING
Slide 100
Slide 100 text
IN SUMMARY
Slide 101
Slide 101 text
KNOW WHAT’S IMPORTANT TO YOUR USERS
Slide 102
Slide 102 text
IDENTIFY HOW YOUR SYSTEM WILL DEGRADE
Slide 103
Slide 103 text
IDENTIFY POINTS OF FAILURE AND BUILD IN FAIL-SAFES
Slide 104
Slide 104 text
LEARN FROM EVERY FAILURE
Slide 105
Slide 105 text
THANK YOU IAN FEATHER - BUZZFEED - @IANFEATHER