Rex Scale-up: The Impacts of Scaling Up
summary
A software company in the energy sector grew from 7 to 77 developers in three years and describes the technical, organizational, and operational impacts of that scale-up. Topics include Infrastructure as Code and limited ops staffing, strategies for evolving a codebase with many more developers, breaking up an oversized monolith (modularization, DDD), team structuring influenced by Conway’s Law, and lessons learned from successes and failures.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:10Scaling growth and challenges
- 6:04Technical migration and architecture
- 8:54Cloud migration and automation
- 11:01Team recruitment and onboarding
- 12:47Autonomous team reorganization
- 16:19Team splitting criteria
- 20:12Modularization benefits and challenges
- 24:27Inter-team coupling management
- 27:15Lambda and containers experience
- 30:26Shared technical components and conventions
- 32:12Quality improvement and testing
- 34:40Practice communities and silos
- 37:07Security and access management
- 38:10Bootstrapping and golden path
- 40:21Prioritization with delay cost
- 41:02Current evolutions and outlook
related talks
26mScaling engineering organizations
56mScaling Up!
25mScaling Up, Not Out: Managing Enterprise Demands in a Growing SaaS Startup
18mScaling DevOps in Complex Environments: Challenges, Failures, and Successes
42mScaling Data at Ovoko: The Succesful Strategy
46mDigital scale-up architectural patterns
14mGrowing pains: Scaling and re-architecting systems under fire
52mDevops @Scale