If I had it to do again
summary
FireHydrant rebuilds would lean hard on specific infrastructure choices: the Laddertruck Rails codebase grew to 440 public API endpoints (roughly 200 more than a long‑standing competitor), a Grape API approach became brittle, and protocol buffers + gRPC + Envoy (with Gnostic → OpenAPI) replace it. Background work uses Temporal for durable workflows (three+ years in production), PubSub proves rock‑solid over seven years, Sidekiq stays for trivial retries, CQRS and account_id/org_id columns fix audit, multi‑org and deletion pain, and polymorphic actor fields are flagged as a costly mistake.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 5:30Talk agenda
- 7:37Rails API with Grape mistake
- 12:37Protocol buffers and gRPC
- 24:39Background job tools
- 27:10Temporal for workflows
- 35:16CQRS and app design
- 37:24Actor polymorphism mistakes
- 42:41Summary and closing
- 43:47Q&A
related talks
32mRefactoring Legacy Apps with APIs and Messages
01h 07mA year with Hanami in production: the Good, the Bad and some Recipes
33mOpen Sourcing: Real Talk
20mSafely Decomposing a Highly Available Rails App
51m"A year with Hanami in production: the Good, the Bad and some Recipes"
42mHow Rails fosters a diverse and competitive tech ecosystem in the era of big tech
46m365 Days Later: Moving from Java to RoR and how it changed everything
30mSome Funny Things Happened on The Way to A Service Ecosystem