Technically, a Talk
summary
Rails gains first-class database configuration objects and a pool manager for sharding after ~100 pull requests over 2.5 years, upstreaming GitHub’s hacks and deleting thousands of lines of internal code. Migrations and named rails tasks now work across writers, replicas and shards; models use connects_to/connected_to to establish connections per abstract class. An automatic role-swapping middleware guarantees read‑your‑own‑write with a default two‑second delay. Feature ships in Rails 6+, sharding APIs exist but automatic shard switching remains manual.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:55Welcome
- 8:59Architecture
- 12:24Database Configuration Objects
- 15:13Rails
- 20:31Connects
- 22:28Connected2 API
- 26:46Automatic Role Swapping
- 29:51Thank you
- 30:29Multiple databases in Rails
- 34:16Rails Foundation
- 36:58Conclusion
related talks
41mKeynote: Technically, a Talk
01h 09mAll the Things I Thought I Couldn't Do
48mKeynote: The Future of Rails 6: Scalable
56mScaling Rails API to Write-Heavy Traffic
43mThe Magic of Rails
39mPostgres & Rails 6 Multi-DB: Pitfalls, Patterns, Performance
24mRails 5 Features You Haven't Heard About
24mThe Rails Features we Loved, Lost, and Laughed at