How we place Ruby Hanami from a PoC into a Production ready application at BankFacil.
This talk is Part of First Hanami SP Meetup in Sao Paulo/Brazil
Follow: #hanamirb_sp / #hanamirb
5. ”What's this
application do?”
”Why should the
top level directory
structure
communicate that
information?”
Ruby Midwest 2011 - Keynote: Architecture the Lost Years by Robert Martin
(https://www.youtube.com/watch?v=WpkDN78P884)
6. ”The web is a detail”
”The web is a delivery
mechanism!”
Ruby Midwest 2011 - Keynote: Architecture the Lost Years by Robert Martin
(https://www.youtube.com/watch?v=WpkDN78P884)
7.
8. Back in October/2015 – Hanami was called Lotus
http://hanamirb.org/blog/2016/01/22/lotus-is-now-hanami.html
Starting up a Proof of Concept
12. PoC’s Final Presentation
The idea was gain the ”green card” from our tech team to starting the project with this structure
https://github.com/hlegius/hanami-rails-as-frontend
13. Right after* PoC’s approval
All frontend-related stuff goes to
applications
Actually, it was 5-7 days after PoC’s approval =P
14. Release v0.99
=> /web
Form Objects
Grape gem
JSON API Spec Representation
Hanami Validations
Domain Model
(Hanami Model)
DDD Boundaries
(Infra & Application layers)
Rake Tasks
17. Good bye Rails; Hello Hanami (again)
Changes applied in Production env in 5 working days
18. Final considerations
• Your team must be engaged and
accept the adoption
• You can not do this alone! (read it
multiple times)
• PoC is a game changer
• Practice; Practice; Practice*
• Hanami v0.7.3 is not ready for
production, they say.
* The Passionate Programmer - Chad Fowler – The Pragmatic Bookshelf