Rack based web apps with JRuby and TorqueBox
summary
JRuby runs on the JVM and delivers concrete speedups: Fibonacci 40: MRI ~53s, JRuby 10.4s. A Sinatra + Puma JSON-encode benchmark shows MRI ~25s, JRuby first 8.5s then warm <3s while using all CPU cores because JRuby uses native threads (no GIL). TorqueBox provides queues, topics, scheduled jobs, HornetQ, Infinispan and Quartz, STOMP-backed WebSockets, and background processors with on_message/on_error; deploy as a WAR or via Capistrano. Example: generate PDFs with the Flying Saucer + iText Java libraries.
AI-written summary · about
chapters (17)
- 0:00Introduction and speaker
- 1:19What is JRuby
- 2:23JRuby performance benchmarks
- 7:21Threads vs processes in JRuby
- 8:27Using Java libraries in Ruby
- 10:53JRuby ecosystem benefits
- 11:58Rails app scaling challenges
- 12:20TorqueBox overview
- 14:32TorqueBox background jobs
- 17:45Topics and messaging
- 18:50WebSockets with TorqueBox
- 21:30Personal experience with JRuby
- 22:24Q&A: Multi-app TorqueBox
- 24:15Q&A: Deployment strategies
- 25:38Q&A: JRuby gem compatibility
- 27:34Q&A: Java integration
- 28:51Q&A: Performance comparison
