Tweet
Tweet

Slide 1

Slide 1 text

No content

Slide 2

Slide 2 text

Village

Slide 3

Slide 3 text

Open landscape

Slide 4

Slide 4 text

Street

Slide 5

Slide 5 text

City

Slide 6

Slide 6 text

City

Slide 7

Slide 7 text

Crumbling street

Slide 8

Slide 8 text

Building maintenance

Slide 9

Slide 9 text

Big or Small? Stand up if in your codebase you… • have more than 50 models • have a class with more than a 1000 LOC • have an ActiveRecord model with more than 30 :has_many • can’t run your full test suite on your machine • can’t run your test suite on your machine in under 20 minutes

Slide 10

Slide 10 text

Street

Slide 11

Slide 11 text

Structural Engineering in Ruby Stephan Hagemann

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

The only thing that ultimately let’s you reign in complexity within one app are components

Slide 14

Slide 14 text

As a language, Ruby does not have components

Slide 15

Slide 15 text

Gems can act as components

Slide 16

Slide 16 text

…they work well

Slide 17

Slide 17 text

For Rails, the situation kinda sucks…

Slide 18

Slide 18 text

…but works ok

Slide 19

Slide 19 text

Let’s make it better!

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

No content

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

No content

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

Just a normal Rails app
 with some extra structure…

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

Structural 
 Costs + Benefits

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

Method 2 LOC Costs Hide logic Benefits Allow Reuse

Slide 45

Slide 45 text

Class 2 LOC Costs Bundle logic and data Benefits Allow Reuse

Slide 46

Slide 46 text

Namespace 2 LOC Costs Prevent naming collisions in the global namespace Benefits Group 
 classes 
 and methods

Slide 47

Slide 47 text

Component

Slide 48

Slide 48 text

WHAT IS A COMPONENT?

Slide 49

Slide 49 text

Labeled Content + Explicit Dependencies

Slide 50

Slide 50 text

Labeled, Unique Content + Explicit, Directed, Acyclic Dependencies

Slide 51

Slide 51 text

@shageman cbra.info ?

Slide 52

Slide 52 text

@shageman cbra.info

Slide 53

Slide 53 text

@shageman cbra.info ? ?

Slide 54

Slide 54 text

Labeled, Unique Content + Explicit, Directed, Acyclic Dependencies

Slide 55

Slide 55 text

@shageman cbra.info

Slide 56

Slide 56 text

A depends on B … A B

Slide 57

Slide 57 text

thus B can not depend on A A B X

Slide 58

Slide 58 text

… and you can’t cheat A B X C

Slide 59

Slide 59 text

No content

Slide 60

Slide 60 text

No content

Slide 61

Slide 61 text

Structure Benefit Cost Method Allow reuse, 
 hide logic 2 Class Bundle logic and data, allow reuse 2 Namespace Prevent naming collisions, group classes and methods 2

Slide 62

Slide 62 text

Gem

Slide 63

Slide 63 text

Gem 88 LOC Costs Create provably independent
 package of 
 code Benefits bundle gem awesome_lib Allow 
 Distribution

Slide 64

Slide 64 text

Gem + Engine 528 LOC Costs Create provably independent
 package of 
 code with 
 Rails Benefits rails plugin new components/awesome_engine --full --mountable Allow 
 Distribution

Slide 65

Slide 65 text

Structure Benefit Cost Method Allow reuse, 
 hide logic 2 Class Bundle logic and data, allow reuse 2 Namespace Prevent naming collisions, group classes and methods 2 Component Allow Distribution, Create provably independent package of code 88 Rails Component Allow Distribution, Create provably independent package of code with Rails 528

Slide 66

Slide 66 text

No content

Slide 67

Slide 67 text

No content

Slide 68

Slide 68 text

ML predictor X

Slide 69

Slide 69 text

1 component with 100 elements 1,267,650,600,228,230,000,000,000,000,000 2 component with 50 elements 2,251,799,813,685,150 4 component with 25 elements 134,217,624 5 component with 20 elements 5,242,775 10 component with 10 elements 10,130 * assuming a lot of stuff, including complexity growing according to Reed’s law

Slide 70

Slide 70 text

Structure Benefit Cost Method Allow reuse, 
 hide logic 2 Class Bundle logic and data, allow reuse 2 Namespace Prevent naming collisions, group classes and methods 2 Component Allow Distribution, Create provably independent package of code 88 Rails Component Allow Distribution, Create provably independent package of code with Rails 528

Slide 71

Slide 71 text

No content

Slide 72

Slide 72 text

2 LOC Costs

Slide 73

Slide 73 text

Structure Benefit Cost Method Allow reuse, 
 hide logic 2 Class Bundle logic and data, allow reuse 2 Namespace Prevent naming collisions, group classes and methods 2 Component Allow Distribution, Create provably independent package of code 88 Rails Component Allow Distribution, Create provably independent package of code with Rails 528

Slide 74

Slide 74 text

Let’s make it better!

Slide 75

Slide 75 text

Share the stories of your large app!

Slide 76

Slide 76 text

Reduce Rails component costs!

Slide 77

Slide 77 text

Improve CI/CD integrations

Slide 78

Slide 78 text

Fix cross-component 
 dependency versioning

Slide 79

Slide 79 text

Can we create 
 component extractors?

Slide 80

Slide 80 text

Street

Slide 81

Slide 81 text

Building maintenance

Slide 82

Slide 82 text

City

Slide 83

Slide 83 text

Futuristic skyscraper