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

Rails Engines

Rails Engines

Talk from SFRails on 5/23/2013 about using rails engines and how they can accelerate development speed by abstracting business logic, as well as some of the pitfalls of doing them…

Christopher Hein

May 24, 2013
Tweet

More Decks by Christopher Hein

Other Decks in Programming

Transcript

  1. {ENGINES not just for cars anymore_

  2. @christopherhein {ME

  3. {WORK

  4. {HISTORY they really aren’t new_

  5. {2005 engine development commenced…

  6. {DHH All attempts at creating high-level business components that can

    be re-used and re-configured have failed previously “ ”
  7. {ROR around this time he also announced that engines would

    not be a part of the Rails core
  8. {2009 skipping ahead…

  9. {ADDED “ ” Engines: Share reusable application pieces complete with

    routes that Just Work, models, view paths, and the works.
  10. {2013 fast-forward…

  11. {2013 They’re awesome!

  12. {WHY just trust me & lets drink_

  13. {WHY super simple super modular super quick*

  14. {SIMPLE prebuilt generators focused features blazing fast test suites

  15. {MODULAR completely reuseable completely customizable basically limitless

  16. {QUICK just ruby just rails just a gem

  17. {USED all over in the wild_

  18. {USED Rails Admin https://github.com/sferik/rails_admin Devise https://github.com/plataformatec/devise Spree https://github.com/spree/spree

  19. {PITFALLS but they’re avoidable_

  20. {PITFALLS start fresh on every single engine, so… automate

  21. {PITFALLS requires more prep, so… don’t rush it

  22. {FINALLY there are other good things_

  23. {FINALLY THANKS EVERYONE!