Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Component-based Ruby and Rails Architectures @ ...

shagemann
April 05, 2013

Component-based Ruby and Rails Architectures @ Mountain West Ruby 2013

How to organize Ruby and Rails codebases into small(er) components. The 8 steps can be found as tags in the sample repository: github.com/shageman/the_next_big_thing

shagemann

April 05, 2013
Tweet

More Decks by shagemann

Other Decks in Technology

Transcript

  1. (a gorgeous and infinite nothingness with all the bells and

    whistles of active*) Rails Gems Saturday, April 6, 13
  2. The secret to building large apps is never build large

    apps. Justin Meyer Saturday, April 6, 13
  3. The secret to building large apps is never build large

    apps. Break your applications into small pieces. Then, assemble those testable, bite- sized pieces into your big application Justin Meyer Saturday, April 6, 13
  4. 5 looser coupling 3 gems 1 one app 4 engines

    8 HTTP SOA 2 modules 7 eco-system 6 services Saturday, April 6, 13
  5. Remember! a gorgeous and infinite nothingness with all the bells

    and whistles of active* Saturday, April 6, 13
  6. Choose modules that tell the story of the system and

    contain a cohesive set of concepts Eric Evans Saturday, April 6, 13
  7. Rails::Engine allows you to wrap a specific Rails application or

    subset of functionality and share it with other applications or within a larger packaged application. http://edgeapi.rubyonrails.org/classes/ Rails/Engine.html Saturday, April 6, 13
  8. 5 looser coupling 3 gems 1 one app 4 engines

    8 HTTP SOA 2 modules 7 eco-system 6 services Saturday, April 6, 13
  9. 5 looser coupling 3 gems 1 one app 4 engines

    8 HTTP SOA 2 modules 7 eco-system 6 services Saturday, April 6, 13