-
Notifications
You must be signed in to change notification settings - Fork 25
Complex Made Simple: Sleep Better with TorqueBox
Presenter: Lance Ball
Lance Ball is a Senior Software Developer at Red Hat and a core member of the TorqueBox team. He has been writing code for over a dozen years in startups, as a consultant, and working for The Man. His ideas have been expressed in Ruby, Java, Perl and C++. As a consultant, Lance wrote Rails and Sinatra applications before joining Red Hat. He's on Twitter as @lanceball.
Even the simplest of Rails applications can eventually grow into a twisted mess of complexity. At some point you will need a background task, or a long-running service, or a scheduled job, or all of the above and more. All of these little bits of functionality added to an application ad hoc can keep you up at night with cold sweats and nightmares. But it doesn't have to be that way.
In this presentation, we will examine a complex Rails application - complexity that is eventually common to most modern Rails apps: background tasks, scheduled jobs, WebSockets, long-running services, caching and more. We will look at the challenges inherent in these features for both development and deployment. Then we'll look to TorqueBox for simple solutions to these complex problems. You'll never have that long-runing service using the wrong Ruby code again; no more environment variable nightmares in your cron jobs. You can sleep better now.
TorqueBox is a Ruby application server that is built on JRuby and JBoss AS7. It provides asynchronous messaging, scheduled jobs, long-running processes, caching, simple deployment, and much more. TorqueBox is designed to bring the power, scalability and stability of these time-tested JavaEE services to Ruby applications through a simple and expressive Ruby interface.
- This is a file generated from the RailsConf JSON. Please remove this notice when adding notes.
- If you're interested in the generator code, see the "generator" directory.
- This layout is just a suggestion.
- Bullet points might work well. Paragraphs too. Up to you. :)
A crowd-sourced conference wiki!
Working together is better. :)
- Speakers, for example:
- Recent Conferences
- Software
- Offline Access
- Contributors (More than 50!)
- Code Frequency