"Build vs Buy" on Rails
summary
Argues that choosing Rails lets a team keep Ruby everywhere to avoid vendor lock‑in and niche tooling and describes building an internal integration platform called constellation project that uses pure Ruby connectors, Kiba ETL pipelines, and Sidekick Enterprise rate limiting packaged with Shopify’s pack work. Outcome: initial pace of five integrations in a year accelerates to five more in about six weeks, reducing onboarding friction and proving the approach works for now while keeping an escape path to buy later.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:44Why Rails matters
- 3:52Build-buy continuum trade-offs
- 7:01Key build-buy factors
- 11:38Building integrations in-house
- 13:22Buying integration services
- 16:13Rails for integration strategy
- 17:18Designing with Ruby and Rails
- 20:51Integration approach retrospective
- 22:36When to swap build/buy
- 24:23Build-buy shifts examples
- 26:08Managing integration risks
- 27:31Red flags in projects
- 29:20Business-tech alignment
- 30:45Q&A
related talks
34mIndustrial Rails
34mRails: Still the Best Framework for Bootstrapping
15mBig Corps, Big Worries Some points on selling Ruby to Big Corps
27mScaling Ruby Applications: Challenges, Solutions and Best Practices
30mThe Rails Story: Two Decades of Design and Decisions
52mKeynote: Startups on Rails in 2024
43mThis is Not a Rails Shop
42mRuby on Rails - The Single Engineer Framework