Talks
Speakers
Events
Topics
Search
Sign in
Search
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
search talks for
⏎
Suggest modification to this talk
Title
Description
As Rails applications grow over time, organizations ask themselves: 'What’s next? Should we stay the course with a monolith or migrate to microservices?' At @Shopify they chose to modularize their monolith, but after 6 years they are asking: 'Did we fix what we set out to fix? Is this better than before?' Join Rails Core member Eileen Uchitelle as she poses these questions during her #RailsWorld Day 2 Opening Keynote. #RubyonRails #Rails #Rails8 #monolith #microservices #modularization #scaling Thank you Shopify for sponsoring the editing and post-production of these videos. Check out insights from the Engineering team at: https://shopify.engineering/ Stay tuned: all 2024 Rails World videos will be subtitled in Japanese and Brazilian Portuguese soon thanks to our sponsor Happy Scribe, a transcription service built on Rails. https://www.happyscribe.com/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video features Eileen Uchitelle's keynote titled "The Myth of the Modular Monolith," delivered at Rails World 2024. In her address, she discusses the evolution of Rails applications as organizations grow and the dilemma they face between maintaining a monolith or transitioning to microservices. Shopify, where Eileen works, opted to modularize their monolith over six years ago, but it has led to reflection on whether this change truly resolved the problems at hand. Key points discussed include: - **Challenges of Growing Rails Applications**: As applications expand, they face issues such as lack of organization, slow CI, and difficulty onboarding new developers. These challenges often lead organizations to consider microservices as a potential solution. - **What is a Modular Monolith?**: Eileen explains that a modular monolith organizes a codebase into modules to alleviate the complexities of large applications while maintaining the deployment benefits of a monolith. - **Myth of Simplification**: She emphasizes that moving to a modular monolith does not inherently fix architectural, operational, or organizational problems. The solutions to these issues often stem from cultural and human challenges rather than technical architecture. - **Common Problems and Their Source**: It categorizes problems into architectural, operational, and organizational issues. Organizational challenges are often exacerbated by increasing scale and growth, highlighting a need for improved structure in large applications. - **Misaligned Incentives**: Uchitelle discusses how companies tend to prioritize shipping features over maintaining code quality, leading to technical debt that eventually makes applications unwieldy. - **Recommendations for Improvement**: She stresses the need for better education and indoctrination for developers to embrace Rails conventions and cultivate a positive engineering culture that values quality work. Ultimately, the conclusion presented throughout the keynote emphasizes that modularization should not be seen as a silver bullet but rather an approach that requires diligent work on human and cultural problems to truly improve application architecture and developer satisfaction.
Suggest modifications
Cancel
