Slide 1

Slide 1 text

CAN TIME-TRAVEL KEEP YOU FROM BLOWING UP THE ENTERPRISE? @DAVETRON5000

Slide 2

Slide 2 text

SCALING RAILS

Slide 3

Slide 3 text

SCALING RAILS ▸ Do stuff Faster? ▸ Do more stuff at once?

Slide 4

Slide 4 text

SCALING RAILS ▸ Do stuff Faster? ▸ Do more stuff at once? NO, IT'S ACTUALLY… ▸ Growing Team ▸ Growing Business ▸ Changing Business

Slide 5

Slide 5 text

MONOLITH? OR MICROSERVICES?

Slide 6

Slide 6 text

A FRAMING DEVICE CAUSE & EFFECT

Slide 7

Slide 7 text

DON'T BLOW UP THE ENTERPRISE

Slide 8

Slide 8 text

DON'T BLOW UP THE ENTERPRISE

Slide 9

Slide 9 text

DON'T BLOW UP THE ENTERPRISE

Slide 10

Slide 10 text

DON'T BLOW UP THE ENTERPRISE

Slide 11

Slide 11 text

DON'T BLOW UP THE ENTERPRISE

Slide 12

Slide 12 text

FIRST, SOME ASSUMPTIONS

Slide 13

Slide 13 text

FIRST, SOME ASSUMPTIONS ▸ Over time, more people will work on the code

Slide 14

Slide 14 text

FIRST, SOME ASSUMPTIONS ▸ Over time, more people will work on the code ▸ Over time, different people will work on the code

Slide 15

Slide 15 text

FIRST, SOME ASSUMPTIONS ▸ Over time, more people will work on the code ▸ Over time, different people will work on the code ▸ There will be increasing demands on the code

Slide 16

Slide 16 text

FAILURE: BUSINESS/PRODUCT NOT MEETING USER NEEDS ▸ Simple changes difficult ▸ Difficult changes impossible ▸ Low morale ▸ Brain drain

Slide 17

Slide 17 text

COMMON, BUT NOT UNIVERSAL ▸ Start-up ▸ New project on a larger company ▸ New longer-term consulting gig

Slide 18

Slide 18 text

COMMON, BUT NOT UNIVERSAL ▸ Start-up ▸ New project on a larger company ▸ New longer-term consulting gig GROWTH & CHANGE

Slide 19

Slide 19 text

NOTHIN' BEATS MONOLITH! GOOD 'OLE MONOLITH

Slide 20

Slide 20 text

SHIP EARLY, SHIP OFTEN INTEGRATED SYSTEM

Slide 21

Slide 21 text

MORE DEVELOPERS!

Slide 22

Slide 22 text

MORE DEVELOPERS!

Slide 23

Slide 23 text

MORE DEVELOPERS!

Slide 24

Slide 24 text

MORE HIDDEN COMPLEXITY HOMEPAGE ADMIN PURCHASING SEARCH REFERRALS

Slide 25

Slide 25 text

MORE HIDDEN COMPLEXITY ADMIN.CSS HOMEPAGE ADMIN PURCHASING SEARCH REFERRALS

Slide 26

Slide 26 text

MORE HIDDEN COMPLEXITY ADMIN.CSS HOMEPAGE ADMIN SEARCH REFERRALS

Slide 27

Slide 27 text

MORE HIDDEN COMPLEXITY ADMIN.CSS HOMEPAGE ADMIN SEARCH CACHE REFERRALS

Slide 28

Slide 28 text

MORE HIDDEN COMPLEXITY ADMIN.CSS HOMEPAGE ADMIN CACHE REFERRALS

Slide 29

Slide 29 text

ENTANGLEMENTS

Slide 30

Slide 30 text

ENTANGLEMENTS user.signed_up.chronologically.approved. active_orders.in_zip(:east_cost). unshipped.first.try(:first_name)

Slide 31

Slide 31 text

ENTANGLEMENTS

Slide 32

Slide 32 text

ENTANGLEMENTS after_create do |user| end

Slide 33

Slide 33 text

ENTANGLEMENTS after_create do |user| end UserMailer.send_welcome(user.id)

Slide 34

Slide 34 text

ENTANGLEMENTS after_create do |user| end UserMailer.send_welcome(user.id) PaymentProcessor.add_customer(user.id)

Slide 35

Slide 35 text

ENTANGLEMENTS after_create do |user| end UserMailer.send_welcome(user.id) PaymentProcessor.add_customer(user.id) MarketingTrackingSite.event!(user.id)

Slide 36

Slide 36 text

ENTANGLEMENTS after_create do |user| end UserMailer.send_welcome(user.id) PaymentProcessor.add_customer(user.id) MarketingTrackingSite.event!(user.id) OtherTrackingSite.event!(user.id)

Slide 37

Slide 37 text

OH, AND… ▸ Test suite is glacial ▸ Don't even think about looking in app/assets/javascripts ▸ /admin starts acting up -> www is dead, too ▸ Etc.

Slide 38

Slide 38 text

REMEMBER WHAT FAILURE LOOKS LIKE? ▸ Simple changes difficult ▸ Difficult changes impossible ▸ Low morale ▸ Brain drain

Slide 39

Slide 39 text

REMEMBER WHAT FAILURE LOOKS LIKE? ▸ Simple changes difficult ▸ Difficult changes impossible ▸ Low morale ▸ Brain drain

Slide 40

Slide 40 text

MICROSERVICES FROM DAY 1 NEVER AGAIN

Slide 41

Slide 41 text

BEFORE EVEN STARTING…

Slide 42

Slide 42 text

BEFORE EVEN STARTING… ▸ Deploy lots of apps

Slide 43

Slide 43 text

BEFORE EVEN STARTING… ▸ Deploy lots of apps ▸ Authentication

Slide 44

Slide 44 text

BEFORE EVEN STARTING… ▸ Deploy lots of apps ▸ Authentication ▸ Versioning

Slide 45

Slide 45 text

BEFORE EVEN STARTING… ▸ Deploy lots of apps ▸ Authentication ▸ Versioning ▸ JSON format

Slide 46

Slide 46 text

BEFORE EVEN STARTING… ▸ Deploy lots of apps ▸ Authentication ▸ Versioning ▸ JSON format ▸ Which HTTP library?

Slide 47

Slide 47 text

BEFORE EVEN STARTING… ▸ Deploy lots of apps ▸ Authentication ▸ Versioning ▸ JSON format ▸ Which HTTP library? ▸ Argue about REST and status codes

Slide 48

Slide 48 text

OH, AND WHAT SERVICES DO WE ACTUALLY NEED?

Slide 49

Slide 49 text

THREE MONTHS LATER

Slide 50

Slide 50 text

THREE MONTHS LATER ▸ React front-end

Slide 51

Slide 51 text

THREE MONTHS LATER ▸ React front-end ▸ Hits the Backend-for-frontends (BFF)

Slide 52

Slide 52 text

THREE MONTHS LATER ▸ React front-end ▸ Hits the Backend-for-frontends (BFF) ▸ BFF talks to the underlying auth service

Slide 53

Slide 53 text

THREE MONTHS LATER ▸ React front-end ▸ Hits the Backend-for-frontends (BFF) ▸ BFF talks to the underlying auth service ▸ Then hits the role service

Slide 54

Slide 54 text

THREE MONTHS LATER ▸ React front-end ▸ Hits the Backend-for-frontends (BFF) ▸ BFF talks to the underlying auth service ▸ Then hits the role service ▸ Then decorates with the consumer data

Slide 55

Slide 55 text

THREE MONTHS LATER ▸ React front-end ▸ Hits the Backend-for-frontends (BFF) ▸ BFF talks to the underlying auth service ▸ Then hits the role service ▸ Then decorates with the consumer data ▸ To render “Hello, #{first_name}!”

Slide 56

Slide 56 text

THREE MONTHS LATER ▸ React front-end ▸ Hits the Backend-for-frontends (BFF) ▸ BFF talks to the underlying auth service ▸ Then hits the role service ▸ Then decorates with the consumer data ▸ To render “Hello, #{first_name}!” ▸ Managed by Docker, Ansible, AWS, Terraform, Vault, Bash, and, of course, some Go

Slide 57

Slide 57 text

WHAT HAPPENED?

Slide 58

Slide 58 text

WHAT HAPPENED? ▸ Money has been spent

Slide 59

Slide 59 text

WHAT HAPPENED? ▸ Money has been spent ▸ Blog posts all over Hacker News

Slide 60

Slide 60 text

WHAT HAPPENED? ▸ Money has been spent ▸ Blog posts all over Hacker News ▸ Meetups have been attended

Slide 61

Slide 61 text

WHAT HAPPENED? ▸ Money has been spent ▸ Blog posts all over Hacker News ▸ Meetups have been attended ▸ No actual business value

Slide 62

Slide 62 text

WHAT HAPPENED? ▸ Money has been spent ▸ Blog posts all over Hacker News ▸ Meetups have been attended ▸ No actual business value ▸ Nothing to show

Slide 63

Slide 63 text

WHAT HAPPENED? ▸ Money has been spent ▸ Blog posts all over Hacker News ▸ Meetups have been attended ▸ No actual business value ▸ Nothing to show ▸ Is there any money left?

Slide 64

Slide 64 text

REMEMBER WHAT FAILURE LOOKS LIKE? ▸ Simple changes difficult ▸ Difficult changes impossible ▸ Low morale ▸ Brain drain

Slide 65

Slide 65 text

REMEMBER WHAT FAILURE LOOKS LIKE? ▸ Simple changes difficult ▸ Difficult changes impossible ▸ Low morale ▸ Brain drain

Slide 66

Slide 66 text

LET'S DO THIS OK MONOLITH

Slide 67

Slide 67 text

AS LONG AS WE _NOTICE_ THE MESS, WE CAN CLEAN IT UP —Pat Agîlecønßultånt

Slide 68

Slide 68 text

MORE DEVELOPERS!

Slide 69

Slide 69 text

MORE DEVELOPERS!

Slide 70

Slide 70 text

MORE HIDDEN COMPLEXITY HOMEPAGE ADMIN PURCHASING SEARCH REFERRALS

Slide 71

Slide 71 text

MORE HIDDEN COMPLEXITY ADMIN.CSS HOMEPAGE ADMIN CACHE REFERRALS NOW, IT’S TOO MESSY!

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

MORE HIDDEN COMPLEXITY HOMEPAGE ADMIN PURCHASING SEARCH REFERRALS

Slide 74

Slide 74 text

MORE HIDDEN COMPLEXITY HOMEPAGE ADMIN PURCHASING REFERRALS PROMO CODES

Slide 75

Slide 75 text

CLEANING THE AIRPORT BATHROOM ▸ Requires top engineers ▸ Grueling ▸ Small changes difficult ▸ Bigger changes become delayed

Slide 76

Slide 76 text

REMEMBER WHAT FAILURE LOOKS LIKE? ▸ Low morale ▸ Brain drain

Slide 77

Slide 77 text

REMEMBER WHAT FAILURE LOOKS LIKE? ▸ Low morale ▸ Brain drain

Slide 78

Slide 78 text

THERE _IS_ ANOTHER WAY NO BLUR,

Slide 79

Slide 79 text

WHILE IT'S IMPOSSIBLE TO PREDICT THE FUTURE, WE DON'T NEED TO ACT BLIND TO IT. Chris Reasonable

Slide 80

Slide 80 text

DON'T BE BLIND TO THE FUTURE ▸ More developers, more features, more code, more changes ▸ You'll want things decoupled; but not exactly what. ▸ Don't make a mess in the first place

Slide 81

Slide 81 text

ENABLE DECOUPLING ▸ One rails app per business function ▸ No business logic in Active Record models ▸ Use the Rule of Three to guide decisions around abstraction, tooling, de- coupling, and general pattern identification.

Slide 82

Slide 82 text

RULE OF THREE ▸ 1st and 2nd times aren't a pattern. ▸ 3rd time is - use that to create needed tooling or process changes ▸ This is engineering culture ▸ Mature teams can graduate to the Rule of Two :) Effort 1ST 2ND 3RD 4TH 5TH 6TH

Slide 83

Slide 83 text

EXAMPLES ▸ Third Rails app - create it with a re-usable generator ▸ Third Ruby Gem - create it with a re-usable gem scaffold ▸ Third mess you make with jQuery - consider a front-end framework ▸ Third time customers report an outage - improve monitoring

Slide 84

Slide 84 text

WWW SHARED DATABASE

Slide 85

Slide 85 text

WWW CUSTOMER SERVICE SHARED DATABASE

Slide 86

Slide 86 text

WWW CUSTOMER SERVICE MARKETING SHARED DATABASE

Slide 87

Slide 87 text

WWW CUSTOMER SERVICE MARKETING SHARED DATABASE SHARED MODELS SHARED MODELS SHARED MODELS

Slide 88

Slide 88 text

WWW CUSTOMER SERVICE MARKETING SHARED DATABASE SHARED MODELS SHARED MODELS SHARED MODELS PROMO CODE LOGIC PROMO CODE LOGIC

Slide 89

Slide 89 text

WWW CUSTOMER SERVICE MARKETING SHARED DATABASE SHARED MODELS SHARED MODELS SHARED MODELS PROMO CODE LOGIC PROMO CODE LOGIC CACHE

Slide 90

Slide 90 text

WWW CUSTOMER SERVICE MARKETING SHARED DATABASE SHARED MODELS SHARED MODELS SHARED MODELS PROMO CODE LOGIC PROMO CODE LOGIC CACHE

Slide 91

Slide 91 text

WWW CUSTOMER SERVICE MARKETING SHARED DATABASE SHARED MODELS SHARED MODELS SHARED MODELS ANALYTICS PROMO CODE LOGIC PROMO CODE LOGIC CACHE

Slide 92

Slide 92 text

WWW CUSTOMER SERVICE MARKETING FINANCE SHARED DATABASE SHARED MODELS SHARED MODELS SHARED MODELS ANALYTICS PROMO CODE LOGIC PROMO CODE LOGIC CACHE

Slide 93

Slide 93 text

WWW CUSTOMER SERVICE MARKETING FINANCE SHARED DATABASE SHARED MODELS SHARED MODELS SHARED MODELS ANALYTICS PROMO CODES HTTP CACHE

Slide 94

Slide 94 text

WWW CUSTOMER SERVICE MARKETING FINANCE SHARED DATABASE SHARED MODELS SHARED MODELS SHARED MODELS ANALYTICS PROMO CODES HTTP CACHE

Slide 95

Slide 95 text

WWW CUSTOMER SERVICE MARKETING FINANCE SHARED DATABASE SHARED MODELS SHARED MODELS SHARED MODELS ANALYTICS PROMO CODES HTTP PRIVATE DATABASE CACHE

Slide 96

Slide 96 text

WWW CUSTOMER SERVICE MARKETING FINANCE SHARED DATABASE SHARED MODELS SHARED MODELS SHARED MODELS ANALYTICS PROMO CODES HTTP PRIVATE DATABASE PRIVATE DATABASE CACHE

Slide 97

Slide 97 text

YOUR ARCHITECTURE ISN'T EVER "DONE"

Slide 98

Slide 98 text

YOUR ARCHITECTURE PLANS SHOULD BE HOW IT CHANGES NOT WHAT IT SHOULD BE

Slide 99

Slide 99 text

ENTERPRISE BEGINS

Slide 100

Slide 100 text

WHAT DID WE LEARN EXACTLY? ▸ Don't be blind to the future (this is different than predicting it!) ▸ Write code to enable change ▸ Create a culture of change, based on the Rule of Three ▸ Your architecture must evolve and is never "done" ▸ Don't make a mess

Slide 101

Slide 101 text

25% off CODE RailsConf16 FULL-STACK-RAILS.COM SWENG.ME NEED RANTS ABOUT BAD UX AND JAVASCRIPT? @DAVETRON5000 WANT TO WORK THIS WAY? TECH.STITCHFIX.COM/CAREERS/ FINAL SLIDE OF SELF-PROMOTION