Architecting for the lazy

Preston Sego

NullVoxPopuli

Architecting for the lazy

The story of every app ever

The story of every app ever

"The Plan"

> Customer Demands

> Investor Demands

> Marketing / Sales shenanigans

Inevitable Scope Creep and Technical Debt

• Do things the 'standard' way, to try to not create technical debt
• Don't want to go outside of the rails convention
• Rails way is a simple way
• Anyone knowing rails can just pick up any project.**
• Goal: Fast development
• No thinking about the architecture
• Somehow your app still grows to be a beast

Inline Javascript

Inline Styles

Duplicate Code

Overly coupled code

Spaghetti Code

Copy Paste

is my app too big and hard to maintain?

Yes

Discoverability is low

Why does this happen?

Rails (partially)

Fear of changing the defaults

Options

"Services"

Service is semantically incorrect

♪

"Services"

Trailblazer

Rewrite :-(

Intermediary Solution

Drawers

NullVoxPopuli/drawers

app/�├── channels/�├── models/�│ ├── data/�│ │ ├── post.rb�│ │ └── comment.rb�│ └── graph_data.rb�├── jobs/�├── mailers/�│ └── notification_mailer.rb�└── resources/� ├── posts/� │ ├── forms/� │ │ └── new_post_form.rb� │ ├── controller.rb # or posts_controller.rb� │ ├── operations.rb # or post_operations.rb� │ ├── policy.rb # or post_policy.rb� │ └── serializer.rb # or post_serializer.rb� └── comments/� ├── controller.rb� ├── serializer.rb� └── views/� ├── index.html.erb� └── create.html.erb

Similar Ideas

• Ember: https://github.com/dgeb/rfcs/blob/module-unification/text/0000-module-unification.md
• Redux: http://jaysoo.ca/2016/02/28/organizing-redux-application/
• Robert C Martin: https://www.youtube.com/watch?v=WpkDN78P884 RubyConf 2011 "Boundaries"

Questions?