Download to read offline
Uploaded byEnrico Teotti
Build and maintain large Ruby apps 0.0.1
This document discusses strategies for building and maintaining large Ruby applications. It recommends decomposing an application into components, which can then be developed and deployed incrementally. It also suggests adopting a growth mindset when working with legacy code or existing team members. Components may be grouped by domain or functionality and encapsulated in gems. This modular approach helps manage complexity and allows dividing work across teams.
More Related Content
Similar to Build and maintain large Ruby apps 0.0.1
![Support, Monitoring, Continuous Improvement & Scaling Agentic Automation [3/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day3-cfd-251120170304-ddef8112-thumbnail.jpg?width=640&height=640&fit=bounds)
![[DevFest Strasbourg 2025] - NodeJs Can do that !!](https://cdn.slidesharecdn.com/ss_thumbnails/devfeststrasbourg2025-nodejscandothat-251127142731-da65b6fd-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Full-Stack Development] The Modern Stack: Building Web & AI Appli...](https://cdn.slidesharecdn.com/ss_thumbnails/fs-themodernstackbuildingwebaiapplicationswithserverless-251124030844-388cf04f-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Full-Stack Development] PHP in AI Age: The Laravel Way. (Rizqy Hi...](https://cdn.slidesharecdn.com/ss_thumbnails/fs-phpinaiagethelaravelway-251125012602-ef9d330e-thumbnail.jpg?width=640&height=640&fit=bounds)
Build and maintain large Ruby apps 0.0.1
- 1. build and maintainlarge Ruby applications Enrico Teotti - @agenteo - http://teotti.com enrico.teotti@gmail.com
- 2. build and maintainlarge Ruby applications Enrico Teotti - @agenteo - http://teotti.com enrico.teotti@gmail.com
- 4. Ruby files ina project are ingredients in a recipe
- 5. think the applicationyou’re working on
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13. in Italy everybodygroups ingredients… by colour
- 14. white ingredients green ingredients redingredients
- 15. white ingredients green ingredients classesgrouped by design pattern ls -l app/ controllers helpers models presenters services serializers strategies utils views http://teotti.com/application-directories-named-as-architectural-patterns-antipattern/
- 16.
- 17.
- 18. module Promotions class NewMember private deffetch_member(id) Membership::Finder.new(id) end end end module Blog class AfterPublish private def add_blogger_to_promotion Promotions::NewMember.new end end end
- 19. main Ruby application promotions room decorator namefinderblog membership “If a developer must consider the implementation of a component in order to use it, the value of encapsulation is lost.” Eric Evans
- 20. piadina worktop tiramisu worktop sharedworktop carrot cake worktop pizza worktop
- 21. piadina worktop shared worktop dessertworktop pizza worktop
- 22.
- 23. A C D B E main Ruby application yourhealth plan API drug information claims platform product information membership Conway’s Law “organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations" gem gem gem gem gem dependency dependency dependency dependency dependency http://teotti.com/create-dependency-structures-with-local-ruby-gems/
- 24. $ cd local_gems $bundle gem claims_platform $ bundle gem membership $ bundle gem product_information $ vim claims_platform/claims_platform.gemspec Gem::Specification.new do |s| s.name = 'claims_platform' s.add_runtime_dependency 'membership' s.add_runtime_dependency 'product_information' end $ cat local_gems/claims_platform/Gemfile source 'https://rubygems.org' path '..' gemspec directory where all local gems live$ mkdir local_gems
- 25. A C D B E main Ruby application yourhealth plan API drug information claims platform product information membership Sinatra, Rails, Lotus
- 26. A C D B E main Ruby application yourhealth plan API drug information claims platform product information membership unit tested unit tested unit testedunit tested unit tested
- 27. A C main Ruby application B usingC behaviour without requiring it When you execute A behaviour from the main application first, triggering B (which is using C without depending on it) will not trigger an error. When you trigger B (using C without depending on it) from the main application will not trigger an error loaded in memory, deamon or webserver unit tested unit tested not unit tested
- 28. A C D B E main Ruby application F H IL membership payment API payment platform bank transaction credit card transaction your health plan API drug information claims platform product information membership
- 29. A C D B E main Ruby application F H IL membership payment API payment platform bank transaction credit card transaction your health plan API drug information claims platform product information membership
- 30. A C D B E main Ruby application F H IL membership payment API payment platform bank transaction credit card transaction your health plan API drug information claims platform product information membership
- 31. main Ruby application yourhealth plan API drug information claims platform product information membership membership payment API payment platform bank transaction credit card transaction
- 32. deploy parts ofa Rails app
- 33. EDITORIAL UI PUBLICUI DOMAIN LOGIC editorial_ui.gemspec public_ui.gemspec domain_logic.gemspec Rails web application
- 34. deploy@publicServer $ RUNNING_MODE=publicrails s deploy@editorialServer $ RUNNING_MODE=admin rails s http://teotti.com/deploy-parts-of-a-ruby-on-rails-application/ http://teotti.com/reduce-memory-footprint-requiring-portions-of-your-component-based-rails-applications/ Rails.application.routes.draw do case AppRunningMode.value when :admin mount AdminUi::Engine => "/admin" when :public mount PublicUi::Engine => "/" else mount AdminUi::Engine => "/admin" mount PublicUi::Engine => "/" end
- 35. EDITORIAL UI LEGACYMIGRATIONPUBLIC UI DOMAIN LOGIC editorial_ui.gemspec public_ui.gemspec domain_logic.gemspec Rails web application legacy_migration.gemspec
- 36.
- 37. legacy Ruby applications Itis not age that turns a piece of software into a legacy system, but the rate at which it has been developed and adapted without having been reengineered.
- 38.
- 39.
- 40. incremental re-engineering • Decomposethe legacy system into parts. • Choose one part to tackle at a time. • Put tests in place for that part and the parts that depend on it. • Take appropriate steps to wrap, reengineer, or replace the legacy component. • Deploy the updated component and obtain feedback. • Iterate
- 41. incremental re-engineering • Decomposethe legacy system into parts. • Choose one part to tackle at a time. • Put tests in place for that part and the parts that depend on it. • Take appropriate steps to wrap, reengineer, or replace the legacy component. • Deploy the updated component and obtain feedback. • Iterate
- 42. incremental re-engineering • Decomposethe legacy system into parts. • Choose one part to tackle at a time. • Put tests in place for that part and the parts that depend on it. • Take appropriate steps to wrap, reengineer, or replace the legacy component. • Deploy the updated component and obtain feedback. • Iterate http://teotti.com/reengineer-legacy-rails-applications/
- 43.
- 44. fixed mindset growthmindset team mindsets * the person is so talented * the person is so smart * the person is a CSS ninja * the person is experienced * the person works really hard * the person is passionate about CSS and keeping up to date
- 45. –Norman Kerth “Regardless ofwhat we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.”
- 46. build and maintainlarge Ruby applications Enrico Teotti - @agenteo - http://teotti.com enrico.teotti@gmail.com