2. TorqueBox
Like a JBoss

3. What’s TorqueBox
• JRuby API around JBoss to:
• Run Ruby apps in JBoss AS

4. Who’s TorqueBox?
• Project built and supported by Red Hat
• #torquebox on IRC
• LGPL
• 5 years of active development

5. What’s JRuby
• Ruby on the JVM
• Not a toy
• Runs unmodified Ruby code
• Fast; Real Threads; Java Integration

6. What’s JBoss

7. Why JBoss?
• For an Ordinary Web Application

8. Why JBoss?
• For an Ordinary Web Application
• Just Run Passenger / Gunicorn

9. Why JBoss?
• Ordinary Web Application
• Just Run Passenger / Gunicorn
• And Memcached/Redis for caching

10. Why JBoss?
• Ordinary Web Application
• Just Run Passenger / Gunicorn
• And Memcached/Redis for caching
• And Sidekiq/Celery for background jobs

11. Why JBoss?
• Ordinary Web Application
• Just Run Passenger / Gunicorn
• And Memcached/Redis for caching
• And Sidekiq/Celery for background jobs
• And Cron/Sidetiq for scheduled jobs

12. Why JBoss?
• Ordinary Web Application
• Just Run Passenger / Gunicorn
• And Memcached/Redis for caching
• And Sidekiq/Celery for background jobs
• And Cron/Sidetiq for scheduled jobs
• And EventMachine and Faye for Websockets

13. Why JBoss?
• Ordinary Web Application
• Just Run Passenger / Gunicorn
• And Memcached/Redis for caching
• And Sidekiq/Celery for background jobs
• And Cron/Sidetiq for scheduled jobs
• And EventMachine and Faye for Websockets
• And a Load Balancer

14. Or
• Just Run JBoss

15. What’s in the Tin
• JBoss Web + Rack for running Web applications

16. What’s in the Tin
• JBoss Web + Rack for running Web applications
• Infinispan for caching

17. What’s in the Tin
• JBoss Web + Rack for running Web applications
• Infinispan for caching
• HornetQ/JMS for messaging

18. What’s in the Tin
• JBoss Web + Rack for running Web applications
• Infinispan for caching
• HornetQ/JMS for messaging
• Quartz for scheduled events

19. What’s in the Tin
• JBoss Web + Rack for running Web applications
• Infinispan for caching
• HornetQ/JMS for messaging
• Quartz for scheduled events
• Stilts for STOMP messaging over Websockets

20. What’s in the Tin
• JBoss Web + Rack for running Web applications
• Infinispan for caching
• HornetQ/JMS for messaging
• Quartz for scheduled events
• Stilts for STOMP messaging over Websockets
• mod_cluster/JGroups for clustering/load balancing

21. That’s a lot of stuff
• Can pick and choose
• But it’s all supported
• All within a single JVM, with JVMs clustered
across nodes

22. Torquebox API
• Caching
• Messaging/Backgroundable
• Scheduled Jobs
• Services
• STOMP

23. Caching
• Infinispan Data Grid
• Local memory
• Invalidate across cluster <- Rails Store Default
• Distributed <- Non-Rails Default, most
interesting
• XA Transactions

24. • Configure Rails Cache Store for Torquebox
!
!
• Use the Rails.cache normally
!

25. Caching
• Or Use TorqueBox’s Infinispan API directly

26. Messaging
!
• HornetQ
• Load balancing, Failover, Timeouts, Retries
• Persistent across restarts
• TorqueBox API offers
• Topics (all subscribers get message)
• Queues (first subscriber to pop message gets it)

27. Topics vs Queues

28. • Configure a Topic at deployment
!
!
• Set up a class to process the messages

29. Backgroundable
• Simpler abstraction for fire-and-forget

30. Scheduled Jobs

31. Services
• TorqueBox managed background thread
• Like a daemon
• Can run on a single-node with fail-over to
another node in the cluster

32. WebSockets
• STOMP Protocol
• Ships with client JS library
• Can use Topics and Queues we saw earlier

35. Even More
• Authentication
• Hot deploys
• Dependency Injection

36. I wanna try this!
• rvm install jruby
• gem install rails
• rails new your_app
• echo ‘gem torquebox’ >> Gemfile
• bundle install
• torqeubox run
• torquebox deploy
• OR
• docker run mguymon/torquebox

37. Backstage
• Dashboard monitor for your applications
• Deploys into Torquebox

38. Immutant
• Same thing for Clojure
• Red Hat’s Polyglot strategy
• Escalante for Scala

39. Rough Spots, IMO
• Clustering is non-trivial without multicast
• Logging
• Source is mostly Java
• JBoss configuration is intimidating

40. What’s Next
• Torquebox 4
• Probably Wildfly-based
• aka JBoss 8
• Improved Performance

41. Da Mystery of Torqueboxin’

42. Joe Winter
• jwinter@gmail.com
• @jwinter
• From Sungard Consulting Services
• We’re hiring
• We’re looking for Ruby || Front-end JS || Java
• Come talk to me about JRuby
• We’re hiring