Tweet
Tweet

Slide 1

Slide 1 text

Rails? Keep the good parts and move out the the heavy jobs ——————————— • ——————————— How do I really use Amr Tamimi • @amrnt RailsIsrael • Tel Aviv • October 09, 2013

Slide 2

Slide 2 text

CONTROLLERS MODELS VIEWS as we know it RAILS

Slide 3

Slide 3 text

CONTROLLERS MODELS VIEWS CONCERNS LAYOUTS PRESENTERS PARTIALS MAILERS MIDDLEWARES RACK RAILTIE RAILS • • WORKERS ASSETS PIPELINE as we know it LIVE TEST

Slide 4

Slide 4 text

Ordinary Rails app

Slide 5

Slide 5 text

This is too much, Rails.

Slide 6

Slide 6 text

Problems?

Slide 7

Slide 7 text

Resource Usage it matters

Slide 8

Slide 8 text

Realtime Systems

Slide 9

Slide 9 text

API-first web app

Slide 10

Slide 10 text

and

Slide 11

Slide 11 text

MVC Dead is Some say... http://cirw.in/blog/time-to-move-on

Slide 12

Slide 12 text

KISS BIG & don’t mix

Slide 13

Slide 13 text

Team The working on the same project — but separated

Slide 14

Slide 14 text

so

Slide 15

Slide 15 text

AND GO BIG BREAK THINGS

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

API Client App JSON, XML, ... Controllers Database Presenters Assets Views Images, CSS, JS, ... Workers Layouts, partials, ... Let’s do some stuff in the background Models, logic, ... REST, Auth, ...

Slide 18

Slide 18 text

API Client App RABL, jBuilder Rails - Workers ActiveRecord, DataMapper, ... Grape, Sinatra, E, ... Sidekiq, Resque, DelayedJob ...

Slide 19

Slide 19 text

recap

Slide 20

Slide 20 text

Rails is awesome we all agree

Slide 21

Slide 21 text

Rails is kinda heavy

Slide 22

Slide 22 text

and needs N of machines to scale

Slide 23

Slide 23 text

use the parts that don’t hurt

Slide 24

Slide 24 text

do what makes you happy

Slide 25

Slide 25 text

——————————— • ——————————— Thank you Amr Tamimi @amrnt