Where is my scalable API?
summary
Rails JSON API migrates heavy endpoints to Goliath non-blocking IO server, keeps models and controllers but swaps blocking drivers for EventMachine-friendly adapters, and uses Beanstalk job queue plus Varnish and HAProxy with a Couchbase cluster backend. Result: throughput jumps from ~450 to ~1,300 requests/sec, Amazon instances drop from four to one, background work rises from ~40 to ~200–250 jobs/sec, and the refactor proves both cheaper and faster in production.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 3:18What is an API
- 5:32Struggling mobile API case
- 7:38Scalable API requirements
- 8:44Goliath server introduction
- 12:26Goliath vs traditional servers
- 14:46Reactor pattern in Goliath
- 18:50Callbacks vs fibers
- 21:23Goliath drivers
- 22:52Goliath routing
- 24:18Scaling Goliath servers
- 27:18Couchbase optimization
- 28:44Performance refactoring
- 30:12Optimization results
- 31:38JMeter performance testing
- 32:20Beanstalk job processing
- 33:24Goliath in Rails apps
- 34:53Goliath support
- 35:38Q&A
