Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Rails Engines. It’s more than just a cute name made up of two words both related to trains. Are they plug-ins? Are they microservices? When do we use them? How do we implement them? Why aren’t they used more often? Those are the questions I wish were answered for me when I first learned about Rails Engines. Inspired by Wired’s Explain In 5 Levels series, we will explore Rails Engines and address these quandaries using a variety of techniques, breaking down what engines are and how and when to use them.
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 the RailsConf 2022 presentation titled "The Little Engines That Could," Mina Slater introduces the concept of Rails Engines to developers of varying technical backgrounds. The presentation aims to demystify Rails Engines, exploring how they function, their benefits, and how they differ from other Ruby and Rails constructs. Key Points Discussed: - **Introduction to Rails Engines**: Slater explains that Rails Engines are not standalone but require a host Rails application to operate, similar to a symbiote in Marvel Comics, which relies on a host to thrive. - **Benefits of Using Engines**: The audience learns that Rails Engines can encapsulate related code, enhancing modularity and reducing the cognitive load for developers by breaking complex applications into smaller, manageable pieces. This can also improve testing efficiency by narrowing the focus of tests. - **Comparison with Gems and Plugins**: Slater clarifies how Engines relate to gems and plugins, noting that while all Engines are plugins, not all plugins are Engines. Engines offer more extensive functionalities compared to regular gems and are tightly integrated into the Rails MVC architecture. - **Types of Engines**: There are two main types of Engines: full engines and mountable engines, where mountable engines can run alongside the host application and can share class names without conflicts through namespacing. - **Implementation Steps**: Slater guides the audience through the steps of creating a mountable engine using the Rails plugin generator, providing an overview of the generated file structure and essential configurations needed for testing and integrating the engine into a host application. Significant Examples: - The metaphor of a symbiote like Venom is utilized to illustrate how Rails Engines enhance a host application by providing functionalities it lacks, much like how the symbiote grants superhuman abilities to its host. - A hypothetical case scenario of a consulting company tasked with building an engine for restaurant reviews further solidifies the concepts discussed, showcasing practical applications of Rails Engines. Conclusions and Takeaways: - Slater emphasizes that while this presentation offers foundational knowledge, the topic of Rails Engines holds much deeper complexity and potential applications that warrant further exploration. She encourages developers to consider how they might incorporate Engines into their projects, noting the importance of understanding when and why to use them effectively. Overall, Slater's presentation serves as an encouraging introduction to a resource that is underutilized yet powerful within the Ruby on Rails framework.
Suggest modifications
Cancel
