On Rails

On Rails
Podcast Description
On Rails invites Rails developers to share real-world technical challenges and solutions, architectural decisions, and lessons learned while building with Rails. Through technical deep-dives and retrospectives with experienced engineers in the Rails community, we explore the strategies behind building and scaling Rails applications.Hosted by Robby Russell of Planet Argon.
Podcast Insights
Content Themes
The podcast covers topics such as architectural decisions, technical challenges, and lessons learned in Rails development. Examples of specific episodes include discussions on the transition from Resque to Solid Queue by 37signals, the best practices for handling recurring and long-running jobs, and insights into system design, reliability, and maintainability in Rails applications.

On Rails invites Rails developers to share real-world technical challenges and solutions, architectural decisions, and lessons learned while building with Rails. Through technical deep-dives and retrospectives with experienced engineers in the Rails community, we explore the strategies behind building and scaling Rails applications.
Hosted by Robby Russell of Planet Argon.
In this episode of On Rails, Robby is joined by Ryan Stawarz and Austin Story from Doximity, where Ruby on Rails has powered the core of their platform for over 15 years. The trio digs into how a single Rails monolith has evolved to support 100+ engineers and a mobile-first experience for millions of healthcare professionals. From front-end framework migrations to API architecture, they explore the real-world decisions required to keep a large Rails app resilient and fast-moving.
Ryan and Austin walk us through the team’s adoption of GraphQL, what led them to introduce GraphQL Federation, and how they balance speed with reliability when scaling APIs across domains. They talk about the tradeoffs of maintaining both GraphQL and REST, and how Doximity avoids N+1 query pitfalls using BatchLoader. The conversation also touches on the evolution of their front-end—from Backbone to Vue.js—and why Rails’ flexibility still gives them an edge.
Throughout the episode, they share pragmatic insights into debugging at scale, managing one-off data migrations, and determining when a service should live inside or outside the monolith. They also reflect on their use of tools like Packwerk, AnyCable, and Departure, and how a culture of trust, documentation, and lightweight planning helps Doximity move fast without breaking things.
🧰 Tools & Libraries Mentioned
– Ruby on Rails – The web framework powering Doximity’s monolith and many of their services.
– GraphQL-Ruby – Ruby gem for building GraphQL APIs in Rails.
– BatchLoader– Helps reduce N+1 queries in GraphQL.
– Vue.js – Their chosen frontend framework for building single-page applications.
– Packwerk – Helps enforce modular boundaries in their Rails monolith.
– Departure – Used for safe database migrations on large datasets.
– Thor – Used to run one-off CLI scripts with easier testability.
– rake-ui – Internal tool for triggering Rake tasks via a web UI.
– AnyCable – Go-based replacement for ActionCable to support realtime features at scale.
– Docker – Powers consistent local dev and containerized environments.
– Fi
On Rails is a podcast focused on real-world technical decision-making, exploring how teams are scaling, architecting, and solving complex challenges with Rails.
On Rails is brought to you by The Rails Foundation, and hosted by Robby Russell of Planet Argon, a consultancy that helps teams improve and modernize their existing Ruby on Rails apps.

Disclaimer
This podcast’s information is provided for general reference and was obtained from publicly accessible sources. The Podcast Collaborative neither produces nor verifies the content, accuracy, or suitability of this podcast. Views and opinions belong solely to the podcast creators and guests.
For a complete disclaimer, please see our Full Disclaimer on the archive page. The Podcast Collaborative bears no responsibility for the podcast’s themes, language, or overall content. Listener discretion is advised. Read our Terms of Use and Privacy Policy for more details.