Preparing for Rapid Growth - Tips for Enabling Your App and Team to Grow
summary
iTriage grows from a kitchen table to 5 million downloads in three years and scales by refactoring into Rails Engines and a JSON REST API, moving to Rails 3, and isolating functional modules (clinical, providers, scheduling) while keeping one DB where needed. Deployment uses Chef, automated builds, Solr for search and a separate HL7 integration engine for legacy formats. Mobile release cadence shortens from months to three‑week cycles, QA owns integration tests (Selenium) and the ~20‑person engineering+QA team reports measurably higher velocity.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:50The first stage of growth
- 7:12App development
- 13:56Architecture
- 20:50Management
- 23:00Organization
- 24:31Recruiting
- 25:28Why work on this project
- 28:45Learn more
- 29:29What tools do you use
- 31:03Are you better version
- 31:41Resources
- 33:32Metrics
- 37:53Automation
- 42:38Business Challenges
- 45:53Change in Business Model
related talks
24mLeading the team through a rapid growth
25mFrom 0 to 15 million users
32mHow I architected my big Rails app for success!
11mStarting Small to Growing Big
22mEvolving DevOps Teams and Flexible Organizational Culture
31mManaging Growing Pains: Thinking Big While Being Small
29mMore Engineers, More Problems: Solutions for Big Teams
28mFrom Startup to Scale Up: How to Scale Engineering teams