Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Recorded in June 2018 during https://2018.rubyparis.org in Paris. More talks on https://goo.gl/8egyWi
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
In her talk "The Future of Rails 6: Scalable by Default" at the Paris.rb Conf 2018, Eileen M. Uchitelle discusses the enhancements and future direction of the Ruby on Rails framework, focusing on scalability. She emphasizes the long-standing misconception that Rails cannot scale, despite its successful use by major companies. The session covers two main aspects of Rails scalability: the efficiency of the test suite and the ability to manage increased traffic and data effectively. **Key Points Discussed:** - Eileen introduces her background and involvement with Rails at GitHub, highlighting her work on upgrades and features for future releases. - The need for Rails to overcome its reputation for scalability is underscored through a humorous comparison to Fisher-Price toys, pointing out that both are well-designed and dependable. - Scalability is defined as an application's capability to grow without sacrificing performance over time. Eileen aims to make this process enjoyable for developers. - A crucial aspect of scalability is ensuring that long-running test suites do not hinder development. The introduction of **parallel testing** in Rails 6 is highlighted, allowing developers to run tests concurrently, significantly speeding up testing processes. - The talk outlines the specifics of implementing parallel testing using forked processes and threads, making it easier for developers to run their test suites more efficiently. - Eileen also addresses the management of multiple databases within Rails, which has traditionally been complex and poorly documented. The need for improved **multi-database support** is discussed, emphasizing clearer workflows for migrations and database connections. - The importance of contributing improvements to the Rails community is communicated, advocating for community-driven development of solutions to common scalability issues. - Finally, Eileen concludes with a push for Rails to become inherently scalable by default, encouraging developers to share their experiences and solutions back to the community. **Conclusions and Takeaways:** - Rails can and does scale, albeit with some challenges that will be addressed in upcoming versions. - Enhancements in testing speed through parallelization and better multi-database handling signify a commitment to improving developer experience. - The evolution of Rails relies heavily on community contributions to tackle scaling issues collectively and sustainably, ensuring that Rails meets modern web development demands.
Suggest modifications
Cancel