Keeping Your Massive Rails App From Turning Into a S#!t Show (WindyCityRails 2013)

Keeping Your Massive Rails App From Turning Into a S#!t
Show Thursday, September 12, 13

Keeping Your Massive Rails App From Turning Into a SNAKE

Keeping Your Massive Rails App From Turning Into a CYLON

Keeping Your Massive Rails App From Turning Into a SHEEP

gem “sheep” gem “sheepsafe” gem “sheep-sebastian” gem “SheepDog” Thursday, September
12, 13

Thursday, September 12, 13

Show Benjamin Smith Thursday, September 12, 13

Show Benjamin Smith @benjamin_smith Thursday, September 12, 13

Show By Architecting It For Success Benjamin Smith Success @benjamin_smith Thursday, September 12, 13

Benjamin Smith Success @benjamin_smith Thursday, September 12, 13

Benjamin Smith Success Architecting Rails @benjamin_smith Thursday, September 12, 13

M @benjamin_smith Thursday, September 12, 13

M V @benjamin_smith Thursday, September 12, 13

M C V @benjamin_smith Thursday, September 12, 13

once upon a time @benjamin_smith Thursday, September 12, 13

success Thursday, September 12, 13

long project Thursday, September 12, 13

big dev team Thursday, September 12, 13

lots of codez Thursday, September 12, 13

scalable Thursday, September 12, 13

big bang release Thursday, September 12, 13

success • long project • big dev team • lots
of code • scalable • big 1st release @benjamin_smith Thursday, September 12, 13

a grain of salt @benjamin_smith Thursday, September 12, 13

success • long project • big dev team • lots
of code • scalable • big 1st release @benjamin_smith Thursday, September 12, 13

engines Thursday, September 12, 13

a little background @benjamin_smith Thursday, September 12, 13

the product • Multimedia content publishing • A social network
• iOS app for consumers (using JSON API) • CMS (Rails) for admins @benjamin_smith Thursday, September 12, 13

started simple @benjamin_smith Thursday, September 12, 13

not too bad Thursday, September 12, 13

but why stop there? @benjamin_smith Thursday, September 12, 13

how to get started Thursday, September 12, 13

rails plugin new engine_name --mountable @benjamin_smith Thursday, September 12, 13

gem "engine_name", path: "path/to/engine_name" @benjamin_smith Thursday, September 12, 13

mount EngineName::Engine => "/engine_name", :as => "engine_name" @benjamin_smith Thursday, September
12, 13

rails plugin new engine_name --mountable @benjamin_smith Thursday, September 12, 13

rails plugin new engine_template --mountable @benjamin_smith Thursday, September 12, 13

s/engine_template/new_engine_name/g s/EngineTemplate/NewEngineName/g for file in $(find . -name "*engine_template*") do
mv $file ècho $file | sed s/engine_template/$1/` done @benjamin_smith Thursday, September 12, 13

bundle gem gem_name @benjamin_smith Thursday, September 12, 13

gem "gem_name", path: "path/to/gem_name" @benjamin_smith Thursday, September 12, 13

bundle gem gem_template s/gem_template/new_gem_name/g s/GemTemplate/NewGemName/g for file in $(find .
-name "*gem_template*") do mv $file ècho $file | sed s/gem_template/$1/` done @benjamin_smith Thursday, September 12, 13

got it? got it? Thursday, September 12, 13

engines the right way Thursday, September 12, 13

fully contained engines • all tables namespaced • migrations •
tests @benjamin_smith Thursday, September 12, 13

table namespacing @benjamin_smith Thursday, September 12, 13

migrations inside engines @benjamin_smith Thursday, September 12, 13

rake your_engine_name:install:migrations @benjamin_smith Thursday, September 12, 13

module EngineWithMigrations class Engine < ::Rails::Engine isolate_namespace EngineWithMigrations initializer :append_migrations
do |app| unless app.root.to_s.match root.to_s app.conﬁg.paths["db/migrate"] += conﬁg.paths["db/migrate"].expanded end end end end http://pivotallabs.com/leave-your-migrations-in-your-rails- engines/ Thursday, September 12, 13

one table per migration http://pivotallabs.com/moving-db-tables-between-rails- engines/ Thursday, September 12, 13

testing the engines in isolation @benjamin_smith Thursday, September 12, 13

fully contained engines • all tables namespaced • migrations •
tests @benjamin_smith Thursday, September 12, 13

no circular dependencies @benjamin_smith Thursday, September 12, 13

class User < ActiveRecord::Base has_many :posts end class Post <
ActiveRecord::Base belongs_to :user end Thursday, September 12, 13

domain api Thursday, September 12, 13

domain api • simple classes to wrap ActiveRecord calls •
take as input: params or ids • output PORO @benjamin_smith Thursday, September 12, 13

class UserManager def ﬁnd_by_id(id) User.new(UserRecord.ﬁnd(id)) end private class UserRecord <
ActiveRecord::Base validates :email, presence: true end end Thursday, September 12, 13

ActiveRecord::Base validates :email, presence: true end end class User def initialize(user_record) self.email = user_record.email end end Thursday, September 12, 13

that’s a lie @benjamin_smith Thursday, September 12, 13

it’s called the Data Mapper pattern @benjamin_smith Thursday, September 12,
13

@user.posts @post.user Thursday, September 12, 13

class PostManager def ﬁnd_all_by_user_id(user_id) PostRecord.where(user_id: user_id) # ... convert to
PORO ... end end Thursday, September 12, 13

class PostManager def ﬁnd_all_by_user_id(user_id) PostRecord.where(user_id: user_id) # ... convert to
PORO ... end end post_manager = PostManager.new @posts = post_manager.ﬁnd_all_by_user_id(@user.id) Thursday, September 12, 13

class UserManager def ﬁnd_by_id(id) User.new(UserRecord.ﬁnd(id)) end end Thursday, September 12,
13

class UserManager def find_by_id(id) User.new(UserRecord.find(id)) end end user_manager = UserManager.new
author = user_manager.find_by_id(@post.user_id) Thursday, September 12, 13

no circular dependencies @benjamin_smith Thursday, September 12, 13

started simple Thursday, September 12, 13

I live my life one green build at a time

git whatchanged origin/master.. @benjamin_smith Thursday, September 12, 13

how did it work out? Thursday, September 12, 13

engines are a pain... • LOW velocity for weeks (4-6)
• client worries • opposite of Rails • one pair to start is a MUST • some technical hurtles • must be diligent about refactoring • monkey patching Rails @benjamin_smith Thursday, September 12, 13

... but they get better • no slow down in
development time • they age well • easier parallel development • potential for scaling • smart and fast build scripts @benjamin_smith Thursday, September 12, 13

thumbs up @benjamin_smith Thursday, September 12, 13

ActiveRecord::Base validates :email, presence: true end end Thursday, September 12, 13

thanks Thursday, September 12, 13

more infoz: @benjamin_smith http://pivotallabs.com/tag/rails-application-suites/ https://github.com/benjaminleesmith/sup_locator Thursday, September 12, 13

Keeping Your Massive Rails App From Turning Int...

Keeping Your Massive Rails App From Turning Into a S#!t Show (WindyCityRails 2013)

More Decks by Benjamin Smith

Other Decks in Technology

Featured

Transcript