Sequel: When ActiveRecord is not enough

on YouTube ↗38m

" summary

Claims concrete wins: Sequel yields ~2× faster queries and ~3× fewer allocations in a 1,000-row benchmark versus ActiveRecord, and reads all columns eagerly to avoid hidden lazy costs. Tooling includes a rich expression API (like Arel but public), a Postgres JSONB expression builder, cursor/stream and COPY support, and a plugin model that keeps core small. Connection handling avoids AR pool pitfalls and there’s a reuse ActiveRecord connection gem to integrate Sequel into Rails.

AI-written summary · about

" chapters (15)

1. 0:00Intro
2. 2:45About me
3. 5:30Comparing ActiveRecord and Sequel
4. 8:14ActiveRecord API
5. 9:51ActiveRecord Associations
6. 10:57SQL Design
7. 13:07SQL Complexity
8. 15:04SQL Expressions
9. 18:50eager loading
10. 21:23advanced features
11. 23:27performance
12. 27:25connection pool
13. 29:33SQL in Rails
14. 30:47SQL Models
15. 32:19Conclusion

" related talks

• 28mSequelJeremy Evans · MountainWest RubyConf 2009
• 25mActiveRecord can't do it? Arel can!Vipul A Prathamesh S · Garden City Ruby 2015
• 46mUse PostgreSQL, not Rails, to make Rails Faster!Dan McClain · PostgresOpen 2014
• 21mActiveRecord can't do it? Arel can!Prathamesh Sonpatki, Vipul Amler · Red Dot Ruby Conference 2014
• 35mAdvanced aRel: When ActiveRecord Just Isn't EnoughCameron Dutro · RailsConf 2014
• 28mActive Record Scopes and ArelJacob Swanner · RailsConf 2012
• 32mArel: The Ruby Relational Algebra LibraryBryan Helmkamp · GoGaRuCo 2010
• 29mActiveRecord, the Repository Pattern, and YouCraig Buchek · RailsConf 2019