On Rails — Eddie Galindo & Kagen Hearn: Rate Limiting For Your Customers

Ascend engineering lead Eddie Galindo and senior software engineer Kagen Hearn detailed on the On Rails podcast why the insurance-payments company still runs a single Rails monolith five years in, how the team handled the arrival of much larger customers, and how it found the real limits of its data ingestion pipeline. The 1-hour-24-minute episode also covers feature flags versus database configuration and where AI tooling fits when the software being shipped moves money.

Eddie Galindo https://www.linkedin.com/in/eruva/ is an engineering lead at Ascend https://www.useascend.com/ and Kagen Hearn https://www.linkedin.com/in/kagen-hearn-228b96130 is a senior software engineer there, working on a Rails app that helps insurance agencies move and reconcile money. Robby, Eddie, and Kagen get into why Ascend still runs one Rails monolith five years in, what needed attention when much larger customers started arriving, and how the team went about finding the real limits of their data ingestion pipeline. They also get into feature flags versus database configuration, and where AI tooling fits in when the software you ship moves money. Links: Listen to this episode https://podcast.rubyonrails.org/2462975/episodes/19737744-eddie-galindo-kagen-hearn-rate-limiting-for-your-customers 1h 24m or subscribe to On Rails https://podcast.rubyonrails.org in your podcast player.