Service Oriented Disasters

Slide 1

Slide 1 text

Service Oriented Disasters Ruby Conf Au 2015 @rachelmyers

Slide 2

Slide 2 text

RailsBridge

Slide 3

Slide 3 text

RailsBridge BridgeFoundry

Slide 4

Slide 4 text

Patchwork RailsBridge BridgeFoundry

Slide 5

Slide 5 text

bit.ly/ service oriented disasters

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

1. Complexity is a problem for everyone.

Slide 8

Slide 8 text

1. Complexity is a problem for everyone. 2. Architecture decisions hugely impact code complexity.

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

1. Make each class and method conceptually simple.

Slide 11

Slide 11 text

1. Make each class and method conceptually simple. 2. Reduce complexity in major code paths and in code that changes often.

Slide 12

Slide 12 text

2. Reduce complexity in major code paths and in code that changes often. 3. Complexity in stable code paths is probably acceptable. 1. Make each class and method conceptually simple.

Slide 13

Slide 13 text

2. Reduce complexity in major code paths and in code that changes often. 3. Complexity in stable code paths is more acceptable. 1. Make each class and method conceptually simple.

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

hatsforspacedogs.com

Slide 19

Slide 19 text

Case Study 1: Extracting Tangled Code

Slide 20

Slide 20 text

the javascript

Slide 21

Slide 21 text

# This class encapsulates behavior for hats that are actually for sale as well as hat samples we might sell. class Hat # Public: Adds a Hat to a Cart # Returns the Hat. def add_to(cart) … end # Public: Vote for a sample Hat # Returns True. def vote_yes(user) … end end the ruby

Slide 22

Slide 22 text

# This class encapsulates behavior for hats that are actually for sale as well as hat samples we might sell. class Hat belongs_to :votable_hat, class_name: :Hat # Public: Adds a Hat to a Cart # Returns the Hat def add_to(cart) … end # Public: Vote for a sample Hat def vote_yes(user) … end end

Slide 23

Slide 23 text

Slide 24

Slide 24 text

Problems to solve: 1. Follow Single Responsibility Principle

Slide 25

Slide 25 text

2. Solve “Unrefactorable” javascript Problems to solve: 1. Follow Single Responsibility Principle

Slide 26

Slide 26 text

No content

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

Main DB Mini DB

Slide 29

Slide 29 text

Main DB Mini DB

Slide 30

Slide 30 text

Main DB Mini DB

Slide 31

Slide 31 text

Main DB Mini DB Gem Server

Slide 32

Slide 32 text

1. We drew the wrong lines around services. Failures:

Slide 33

Slide 33 text

2. We didn’t manage our complexity; we reinforced it. 1. We drew the wrong lines around services. Failures:

Slide 34

Slide 34 text

github.com/github/scientist

Slide 35

Slide 35 text

“Easy Rewrites with Ruby and Science” By Jesse Toth

Slide 36

Slide 36 text

Case Study 2: An Identity Service

Slide 37

Slide 37 text

Problems to solve: 1. Manage SpaceDog complexity a.k.a. User

Slide 38

Slide 38 text

Problems to solve: 1. Manage SpaceDog complexity 2. Allow one team to own the model

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

No content

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

1. Added risk & operational complexity. Failures:

Slide 46

Slide 46 text

2. Didn’t simplify anything. 1. Added risk & operational complexity. Failures:

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

Queueing Theory! Request Response Time spent in Main App Time Request Response Time in Identity Service

Slide 49

Slide 49 text

Queueing Theory! Request Response Time spent doing everything Time

Slide 50

Slide 50 text

Deﬁned Team Responsibilities

Slide 51

Slide 51 text

Case Study 3: Sharing Assets Across Applications

Slide 52

Slide 52 text

hatsforspacedogs.com helmets galea fedoras diving-bells

Slide 53

Slide 53 text

hatsforspacedogs.com helmets galea fedoras diving-bells hatsforspacedogs.com helmets galea fedoras diving-bells hatsforspacedogs.com helmets galea fedoras diving-bells hatsforspacedogs.com helmets galea fedoras diving-bells

Slide 54

Slide 54 text

Shared HTML, CSS, JS & Images hatsforspacedogs.com helmets galea fedoras diving-bells hatsforspacedogs.com helmets galea fedoras diving-bells hatsforspacedogs.com helmets galea fedoras diving-bells hatsforspacedogs.com helmets galea fedoras diving-bells

Slide 55

Slide 55 text

Problems to solve: 1. Avoid repeating HTML, CSS, JS and images across applications.

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

No content

Slide 58

Slide 58 text

No content

Slide 59

Slide 59 text

hatsforspacedogs.com helmets galea fedoras diving-bells hatsforspacedogs.com helmets galea fedoras diving-bells hatsforspacedogs.com helmets galea fedoras diving-bells

Slide 60

Slide 60 text

hatsforspacedogs.com helmets galea fedoras diving-bells hatsforspacedogs.com helmets galea fedoras diving-bells hatsforspacedogs.com helmets galea fedoras diving-bells

Slide 61

Slide 61 text

1. Required coordinated upgrades & deployments. Failures:

Slide 62

Slide 62 text

Problems to solve: 1. Avoid repeating HTML, CSS, JS and images across applications. 2. Asset changes should update at the same time.

Slide 63

Slide 63 text

No content

Slide 64

Slide 64 text

GitHub hides this problem.

Slide 65

Slide 65 text

Conclusions

Slide 66

Slide 66 text

1. SOA works for good code, isolated classes with well-defined boundaries Conclusions

Slide 67

Slide 67 text

Conclusions 1. SOA works for good code. 2. SOA works when code needs to run in multiple places.

Slide 68

Slide 68 text

Conclusions 2. SOA works when it needs to run in multiple places. 3. SOA works when it doesn’t create a bottleneck for the main app. 1. SOA works for good code.

Slide 69

Slide 69 text

No content

Slide 70

Slide 70 text

Sam Brown explodingdog.com amazing drawings by (via @kcshearon!)

Slide 71

Slide 71 text

Sam Brown explodingdog.com skirts (and architecture diagrams) by me amazing drawings by (via @kcshearon!)

Slide 72

Slide 72 text

bit.ly/ service oriented disasters @rachelmyers