Architecting Rails Apps

Transcript

1. ARCHITECTING ARCHITECTING RAILS RAILS APPS APPS Studies and thoughts from a Front End perspective.
2. IAGO DAHLEM IAGO DAHLEM Passionate about web and it's ecossystem JavaScript Addicted (also like Ruby) Software Developer at Codeminer 42 Florianópolis
3. WE ARE HIRING! WE ARE HIRING! become@codeminer42.com
4. DISCLAIMERS DISCLAIMERS No code examples :( Keep focus on the theory Don't get it to hard
5. WHY FRONT-END WHY FRONT-END PERSPECTIVE? PERSPECTIVE? Common problems Same responsibilities
8. THE BAD RAILS THE BAD RAILS Built on top of MVC Changes affects other parts of the app Top level structure screams the web framework We don't know what it does
9. "MVC is a delivery design pattern." - Uncle Bob
10. WHAT IS ARCHITECTURE WHAT IS ARCHITECTURE ANYWAY?! ANYWAY?! Independent of technology/framework Makes software easier to change and test
11. Domain layer Application layer Infrastructure layer Input layer
12. DOMAIN LAYER DOMAIN LAYER Entities and business Rules Used by the application layer to de ne use cases Examples: User, Article
13. APPLICATION LAYER APPLICATION LAYER Use cases and actual behavior Interacts with Domain units Adapts the Infrastructure Layer Examples: CreateUser, CreateArticle
14. INFRASTRUCTURE LAYER INFRASTRUCTURE LAYER Interacts with the external world of the application The lowest of them Databases, email services, external APIs Examples: UserRepository, MailChimpService, ArticlesService
15. INPUT LAYER INPUT LAYER The entry point Should only receives user input Returns a response to the user Controllers, CLIs, WebSockets, GUIs Examples: UsersController, ArticlesController
16. SUMMARIZING SUMMARIZING Keep it simple You don't need to use everything Find what works better for and your business Make it fun
17. ADDITIONAL ADDITIONAL INFORMATION INFORMATION The Miners - Scalable Frontend #1 Uncle Bob - Architecture the Lost Years
18. THANKS! THANKS! @iagodahlem iagodahlem.com