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
http://www.rubyconf.org.au Serverless (via AWS Lambda), the new hotness, was definitely something we wanted to explore when developing the backend for our new Virtual Reality app. TLDR - despite expectations to the contrary we came back to Rails, specifically Rails 5 API mode. We'll walk you through our journey, what the different considerations were, what the different strengths of each platform are and how we reached our decision. We think it's essential that as Rails developers we have an understanding of Serverless, both as a replacement and as an augmentation to our skill-set and development environment.
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 "VR Backend Rails vs. Serverless: Froth or Future?" featuring Janet Brown and Ron Ramakrishnan explores the backend development choices for a Virtual Reality (VR) application. The presenters, from Atot Studios, share their journey of developing a collaborative multi-user VR app for a technically proficient client, who initially favored serverless technology (using AWS Lambda). However, after careful consideration, they opted for Ruby on Rails, particularly its API mode. The key points discussed in the video include: - **Understanding the Technologies**: The talk begins with an exploration of the hype surrounding both VR and serverless technologies, emphasizing the need to ground discussions in practical realities rather than buzzwords. - **Client Requirements**: The client sought a VR system enabling six degrees of freedom and real-time interactions among users in various locations, informed their choice of technology. - **Technical Considerations**: The presenters detail the three critical layers needed for VR: a core game engine for physics and animation, a connection layer for user synchronization, and a persistence layer for saving user interactions. - **Evaluation of Serverless**: They clarify that serverless does not imply the absence of servers but a model that abstracts server management to third parties, which can help with scaling but also poses challenges like increased complexity and data management concerns. - **Rails Advantages**: Ultimately, they concluded that Rails offered features conducive to their needs, such as a strong testing infrastructure, integration capabilities, and alignment with client infrastructure. - **Challenges of Serverless**: They discuss the limitations of a serverless approach, including execution time limits, potential latency, and challenges in managing substantial data securely. - **Future Considerations**: The presenters ponder the evolving nature of serverless technology alongside the growth of the VR industry, advocating for a hybrid approach that leverages both serverless and traditional frameworks. In conclusion, the key takeaways include a nuanced understanding of serverless technology as not a one-size-fits-all solution, the robust nature of Rails in handling complex applications, and an invitation for the audience to explore VR development and applications in depth. The discussion highlights the importance of aligning technology choices with project requirements and user experience goals.
Suggest modifications
Cancel
