Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Serverless is widely lauded as the ops-free future of deployment. Serverless is widely panned as a gimmick with little utility for the price. Who’s right? And what does it mean for my Rails app? This session takes a critical look at serverless hosting. We’ll consider the abstractions underlying environments such as AWS Lambda and Google Cloud Run, their assumptions and trade-offs, and their implications for Ruby apps and frameworks. You’ll come away better prepared to decide whether or not to adopt serverless deployment, and to understand how your code might need to change to accommodate it.
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 titled "Serverless Rails: Understanding the pros and cons" presented by Daniel Azuma at RailsConf 2021 critically examines the concept of serverless hosting, particularly in relation to Ruby on Rails applications. The discussion centers around the utility, challenges, and implications of adopting serverless architecture for deploying Rails apps. Key points discussed include: - **Definition of Serverless**: Azuma highlights that "serverless" is a misleading term as it implies the absence of servers, while in fact, underlying infrastructure still relies on servers. The term leads to confusion and misinterpretation of its actual meaning. - **Abstractions in Hosting**: The session delves into the evolution of cloud hosting, from physical servers to virtual machines (AWS EC2), and then to more modern abstractions like Functions as a Service (FaaS) and container services. - **Trade-offs of Serverless**: Azuma explains how while serverless environments offer fewer guarantees (like CPU consistency), they also reduce responsibilities on the developer's part, potentially leading to cost savings. - **Implications for Rails Apps**: The rigidity of Rails as a monolithic framework can complicate serverless implementations. Developers need to consider changes in app initialization, resource management, and data storage when adapting Rails for serverless environments. - **Containers vs. Serverless**: The speaker discusses the advantages of container services (like Google Cloud Run) for Rails apps due to their closer resemblance to traditional server environments. - **Recommendations for Rails Development**: Specific strategies to optimize Rails apps for these environments are provided, including reducing initialization times, avoiding reliance on the file system, and designing more modular applications. - **Future of Rails in New Abstractions**: Azuma expresses the need for the Rails community to adapt to new infrastructures and advocates for a more modular approach in Rails itself, allowing better integration with modern hosting solutions. In conclusion, the session encourages developers to weigh the pros and cons of serverless deployment for Rails applications, while embracing new abstractions and having open discussions to refine their approaches in an evolving technological landscape.
Suggest modifications
Cancel
