Accept Complexity or Reject It? — Reflections Facing a Monolith Raised Alongside Business Growth
summary
A team maintaining an 8‑million‑consultation online telemedicine product built on a monolithic Ruby on Rails app describes how they decide which complexity to accept or reject as the business grows. They use throwaway prototypes and SaaS experiments for uncertain features, intentionally duplicate code to make future discard easy, dogfood the product and observe clinics to learn real constraints, and turn sprint reviews into impact‑focused sessions that track metrics before committing large refactors.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:00Healthcare complexity
- 7:13Balancing complexity
- 10:48Strategic vs tactical
- 13:44Stakeholder engagement
- 15:32Business understanding
- 19:12Sprint reviews impact
- 20:41Conclusion & Q&A
related talks
01h 29mMonolithic Delivery
28mAvoid overengineering & big ball of mud- 7 lessons for maintaining the balance
41mDeconstructing the Monolith
34m"Taming your Rails monolith"
46mDigital scale-up architectural patterns
01h 02mTools for simplified large scale systems
43mThe Clean Architecture: How to Grow From Startup to Enterprise
46mModel Mitosis: Stop making the wrong choice between microservices and monolith