Migrating Shopify’s Core Rails Monolith to Trilogy

on YouTube ↗29m

" summary

Shopify replaces Mysql2 with Trilogy in its largest Rails monolith, adding multi-statement support to the Trilogy Ruby bindings, upstreaming the ActiveRecord adapter into Rails 7.1, and adapting tools like Semian and OpenTelemetry. Rollout runs at 1% of pods, then 100% of a cluster, then full production; CI stays on Mysql2 while daily Trilogy branch tests run. Observed latencies drop from 3.46 ms to 2.7 ms (≈22% faster) and per-query time from 1.49 ms to 1.24 ms.

AI-written summary · about

" chapters (15)

1. 0:00Introduction
2. 0:36Meet Adrianna
3. 2:34Agenda
4. 3:11Climbing a Mountain
5. 3:44What is Trilogy
6. 5:13Why switch to Trilogy
7. 6:31Caveats to Trilogy
8. 7:44Why Trilogy
9. 9:14Making Trilogy a Rails Community Standard
10. 9:30Moving to Trilogy in an Existing Rails App
11. 14:58Other Considerations
12. 18:26External Tooling
13. 22:04Scaling
14. 24:10Upstream Trilogy to Rails
15. 27:14Conclusion

" related talks

• 38mMigrating Shopify’s Core Rails Monolith to TrilogyAdrianna Chang · RailsConf 2023
• 40mHow Shopify Scales RailsJohn Duff · RailsConf 2013
• 41mHow Shopify Scales RailsJohn Duff · Big Ruby 2013
• 23mHow Shopify Sharded RailsCamilo Lopez · Big Ruby 2014
• 33mUpgrading a big application to Rails 5Rafael Mendonça França · RailsConf 2017
• 36mRuby & Rails Versioning at ScaleGeorge Ma · RailsConf 2024
• 32mOperating Rails in KubernetesKir Shatrov · RailsConf 2018
• 22mRiding Rails for decadesRafael Mendonça França · RubyConf Colombia 2016