Future-proofing Your 3rd Party Services

on YouTube ↗33m

" summary

If PayPal gets swapped for Stripe, the codebase keeps working because third‑party calls live in an adapter gem with DTOs and abstract service classes, plus an adapter interface gem shared by app and adapter so the app only uses SRID domain language. Tests run against a VCR cassette plus a test environment that cleans up IDs; cassettes have TTL on CI so breaking changes surface quickly and migration effort becomes a predictable estimate.

AI-written summary · about

" chapters (11)

1. 0:00Start
2. 2:04Third-Party Integration
3. 4:25Teapot Adapter
4. 7:38Define Your Internal Vocabulary
5. 10:16Data Transfer Objects
6. 13:07Abstract Services
7. 15:17Adapter Interface Gem
8. 19:24Basic Rules
9. 21:50Integration Specs
10. 27:02Recap
11. 29:18Cons

" related talks

• 29mMoney Makes Your App Go RoundNoel Rappin · WindyCityRails 2016
• 22mNitty Gritty Service BuildingLauren Voswinkel · RubyConf AU 2015
• 23mAbstracting a Service - A Case Study in Forward Thinking with SOAStuart Corbishley · Rubyfuza 2013
• 22mRiding Rails for decadesRafael Mendonça França · RubyConf Colombia 2016
• 39mDown The Rabbit Hole: An Adventure in Legacy CodeLoren Crawford · RailsConf 2018
• 27mScaling Ruby Applications: Challenges, Solutions and Best PracticesDmitry Sadovnikov · RubyConf AU 2024
• 36mWorking Compassionately with Legacy CodeAmar Shah · RubyConf 2015
• 41m(Re)Building a large scale payments system on RailsMichel Weksler · RailsConf 2015