The Trail to Scale Without Fail: Rails?
summary
Cloudinary runs 15 billion requests per day and relies on a CDN to serve ~95% of traffic, a tiny Go service called seget (Go) handling 85% of cache misses, and Rails for the IO/CPU layers that see about 150M and 125M requests/day respectively. Scaling uses per-cloud sharding, a near‑real‑time cache for multi‑region, a Scala Lobster lock to avoid duplicate transforms, and a Go‑based fair queuing system; these pieces reduce cost and, crucially, actually work in production.
AI-written summary · about
chapters (25)
- 0:00Start
- 1:53Requests per Second
- 5:05What Does cloudinary Actually Do
- 9:12Image Formats
- 10:01Cdns
- 12:04The Delivery Pipeline
- 14:06Auto Scaling
- 15:35Request Life Cycle
- 17:05I O Layer
- 19:20Cdn
- 21:50Invalidation System
- 24:30Advantages of Layers
- 25:32Security
- 26:23Sharding
- 27:08Vertical Partitioning
- 27:37Vertically Partitioning
- 35:06Regions at Cloudinary
- 42:18Best Effort Locking System
- 45:12Downtime
- 45:34How Do You Scale Your Locking System
- 49:19Rate Limits
- 49:52Fair Queuing System
- 56:12Eager Transformations
- 56:41Human Factors
- 58:03Cloudinary on Rails
related talks
27mRails Orbiting the cloud: Mastering the scalability with Kubernetes
38mRails in the Cloud
28mSimplifying at Scale: 7 Years of Rails Architecture
44mIntroduction to application scaling
31mA RAILS PERFORMANCE GUIDEBOOK
40mHow Shopify Scales Rails
37mScaling Rails for Black Friday and Cyber Monday
31mA Rails performance guidebook: from 0 to 1B requests/day
