Crank Up Your Apps With TorqueBox

transcript

MagicRubyFeb 2011

Crank Up Your Apps With

Creative Commons BY-SA 3.0

Jim Crossley

Jim who?

• “recovering java architect”

• java since ’96, ruby since ’06

• emacs and guitars since forever

• Red Hat Senior Engineer

• proud member of

Bob McWhirter

Agenda• High-level BS and Development

Process

• Web, Messaging, Scheduling, Services, Clustering

TorqueBoxthe power of JBoss with the expressiveness of Ruby

TorqueBox: what?

• A “real” app server for Ruby

• Founded in 2008

• Bob’s “labor of love”

• 100% open-source, LGPL license

• Reflects a strong commitment to Ruby from Red Hat

TorqueBox: why?

• “Native” support for Rack apps

• Built-in background processing

• Built-in scheduling

• Built-in clustering

• Easily scalable

• Optionally enterprisey

JRubya good idea done well

JRuby: why?

• Very fast runtime

• Real threads

• Java libraries

• Java tools

• Healthy community

JRuby: why not?

• Slower start up

• Native gems

• FFI

• C extension support

• Some Ruby libs not thread-safe

JBoss ASbut before we get to that...

Enterprise Javamisconceptions

Scary?Is it

Acronymious?

EJBJAR

JAX-RPC

JAX-RS

JAX-WS

JAXPJCK

JDBC JDK

JDOMJEE

JLSJME

JMXJNDI

JNIJNLP JPA

JREJSE

JSP JSR

JSTLJTA

JTS JWS

SAF POJO

WAR SLSB

Bloated?

Bewildering?

Enterprise Java is all thatand more! but...

I promise...

• No XML

• No Java *

• No war files *

• Only Ruby, YAML and...

* Unless you really want to

JBoss ASthe enterprisey good parts

JBoss AS6

• Tomcat for web

• Infinispan for caching

• HornetQ for messaging

• Quartz for scheduling

• mod_cluster for clustering

AS = Application Server

• Not just “web server + interpreter”

• More like initd than httpd

• Can host multiple, disparate apps simultaneously

• Provides basic services to all the apps it hosts

Hot Deployment

• anything added to deploy/ will get deployed

• anything removed from deploy/ will get undeployed

• anything updated in deploy/ will get redeployed

• TorqueBox deployers make JBoss grok YAML and ruby archives

$JBOSS_HOME/server/default/deploy/

Hot Deployment

deployment descriptors

Hot Deployment

zip files (archives)

Development Processhow do they work?

easy install

$ wget http://torquebox.org/torquebox-dev.zip$ unzip torquebox-dev.zip

$ export TORQUEBOX_HOME=$PWD/torquebox-1*$ export JBOSS_HOME=$TORQUEBOX_HOME/jboss$ export JRUBY_HOME=$TORQUEBOX_HOME/jruby

$ export PATH=$JRUBY_HOME/bin:$PATH

easy install

Make sure the jruby found in your path is in $JRUBY_HOME/bin.

easy install

$ jruby -S gem install bundler$ jruby -S gem install rails$ jruby -S gem install sinatra

Rakefile

rake tasks

require "org.torquebox.rake-support"

rake tasks

rake torquebox:run Run TorqueBox server

rake torquebox:deploy[context_path] Deploy the app in the current directory

rake torquebox:undeploy Undeploy the app in the current directory

rake tasks

Start torquebox:run in its own shell and leave it running. Instead of script/server or shotgun or thin or whatever else, use torquebox:deploy.

torquebox:deploy creates a deployment descriptor in the JBoss deploy/ directory

deploy/myapp-rails,rack.yml

application: root: /path/to/myapp env: developmentweb: context: myapp host: www.yourhost.com static: public rackup: config.ruenvironment: MAIL_HOST: mail.yourhost.com REPLY_TO: you@yourhost.com

The fully-qualified path to the app.

This will be the value of either

RAILS_ROOT or RACK_ROOT

The runtime mode of the app. This will be either RAILS_ENV

or RACK_ENV

The app’s context path (or “sub URI”):

http://localhost:8080/myappCan be set via rake:

rake torquebox:deploy[myapp]The default is root:

http://localhost:8080/

A list of virtual hostnames to which

to bind the app.

The location of the app’s static

content, either absolute or relative to the app’s root.

The name of the rackup script used to

boot your app

Any environment variables required

by the app.

• config/torquebox.yml

• internal descriptors have the same structure as the external ones in deploy/

•may be used to provide your own reasonable defaults

Webmake rack, not war

jruby-rack

• All rack-based frameworks supported: rails, sinatra, etc

• No packaging required: apps deploy from where they sit on disk

• No redeploy necessary to see changes when using rack reloading or rails development mode

Gemfile

database connectivity

gem "activerecord-jdbc-adapter"

gem "jdbc-postgres"# gem "jdbc-sqlite3"# gem "jdbc-mysql"

rails template

• Adds TorqueBox rake tasks

• Adds the JDBC sqlite3 gems

• Adds TorqueBox session_store

• Adds Backgroundable module

my first rails app

$ jruby -S rails new myapp -m \ $TORQUEBOX_HOME/share/rails/template.rb

$ cd myapp$ jruby -S bundle install

$ jruby -S rake torquebox:deploy

Messagingasynchronicity

Resque

ActiveMessaging

rufus-scheduler

ConveyorWorkerQueue

CronEdit

lots of options

RailsCronOpen4

Sparrow

Kestral

RabbitMQ

ActiveMQ

Amazon SQS

beanstalkd

starling

workling

async_observer

daemons

BackgroundDRb

BackgroundJob

Background-Fu

DelayedJob

TorqueBox::Messaging

• JMS (Java Message Service) is an API for messaging

•HornetQ is the JBoss JMS implementation

•Task•Backgroundable•MessageProcessor

•Queue•Topic

• No extra tables in your database

• No external system to manage

• Little to no config required at all

• No redeploy necessary in dev mode

• Efficient loading of rails environment

• Automatic load balancing and retries

• Works on Windows, if you care

app/tasks/email_task.rb

class EmailTask < TorqueBox::Messaging::Task def welcome(payload) person = payload[:person] person ||= Person.find_by_id(payload[:id]) if person # send the email person.welcomed = true person.save! end endend

app/controllers/people_controller.rb

class PeopleController < ApplicationController def create @person = Person.new(params[:person]) respond_to do |format| if @person.save EmailTask.async(:welcome, :id => person.id) # respond appropriately end end endend

app/controllers/people_controller.rb

class PeopleController < ApplicationController def create @person = Person.new(params[:person]) respond_to do |format| if @person.save EmailTask.async(:welcome, :id => person.id) # respond appropriately end end endend

Call them from your controllers, models, and observers, or even other tasks. Even in non-Rails apps!

Backgroundable

Inspired by DelayedJob’s handle_asynchronously, it’s trivial to create implicit background Tasks.

lib/something.rb

Backgroundable

include TorqueBox::Messaging

class Something include Backgroundable always_background :foo def foo;; end def bar;; endend...@something.foo@something.background.bar

lib/something.rb

Backgroundable

lib/something.rb

Backgroundable

lib/something.rb

Backgroundable

app/models/slow_poke.rb

Backgroundable

class SlowPoke < ActiveRecord::Base def takes_forever;; end def might_take_awhile;; endend

SlowPoke.always_background :takes_forever

@slowpoke.takes_forever@slowpoke.background.might_take_awhile

Queues

Tasks are built on top of Queues. Of course, you may build your own “MOM” apps by defining your own Queues, Topics, and their message Processors yourself.

config/queues.yml

Queues

/queues/questions:

/queues/answers: durable: false

Processors

You can create a processor class to receive messages from a Topic or Queue

config/messaging.yml

Processors

/topics/print: PrintHandler/queues/popular: - PopularHandler - AdultObserver: filter: "age >= 18" concurrency: 5/queues/students: PrintHandler: config: color: true

Processors

app/models/print_handler.rb

Processors

class PrintHandler < MessageProcessor def on_message(body) puts "Processing #body of #message" end def configure(opts) @color = opts['color'] endend

Queues (again)

But how do you send a message?

example

Queues

include TorqueBoxreq = Messaging::Queue.new '/queues/questions'res = Messaging::Queue.new '/queues/answers' Thread.new do req.publish "What time is it?" puts res.receive( :timeout => 1000 )end puts req.receiveres.publish Time.now

example

Queues

example

Queues

example

Queues

“on the fly”

Queues

include TorqueBox

queue = Messaging::Queue.new '/queues/foo'queue.create ... queue.destroy

Topics

• behavior is different, but interface is the same.

• all subscribers of a topic see each message, but only one subscriber will see any message from a queue

• use topics.yml to define topics

• use TorqueBox::Messaging::Topic

Schedulingget regular later

app/jobs/newsletter_sender.rb

class NewsletterSender def run() subscriptions = Subscription.find(:all) subscriptions.each do |e| send_newsletter( e ) end end end

config/jobs.yml

monthly_newsletter: description: first of month job: NewsletterSender cron: ‘0 0 0 1 * ?’

sandbox: job: Sandbox cron: ‘*/5 * * * * ?’

Seconds Minutes Hours DOM Month DOW Year

0-59 0-59 0-23 1-31? L W

1-12JAN-DEC

1-7SUN-SAT? L #

1970-2099empty

0 */30 10-13 ? * FRI#3

“Fire every half hour from 10am until 1pm on the third Friday of each month”

• More portable. What is the first day of the week on BSD again? What’s cron on Windows?

• Self contained within the app. No external systems to manage and keep in sync.

• Full rails environment loaded and available.

Servicesrun along, lil’ daemon

Services

Long-running, non-web “daemons” that share the runtime environment and deployment lifecycle of your app.

Services

• Represented as a class with optional initialize(Hash), start() and stop() methods, which should each return quickly.

• Typically will start a long-running loop in a thread and respond to external events.

• Configured via services.yml

config/services.yml

Services

IrcBot: server: freenode.net channel: #torquebox publish: /topics/irc

MyMudServer:

SomeOtherService:

app/models,etc/my_service.rb

Services

class MyService def initialize opts= name = opts[:publish] @queue = Messaging::Queue.new(name) end def start Thread.new run end def stop @done = true endend

Services

class MyService def run until @done @queue.publish(Time.now) sleep(1) end endend

Services

class MyService def run until @done @queue.publish(Time.now) sleep(1) end endend

app/services/evented_service.rb

Services

class EventedService def initialize opts= @opts = opts end def start Thread.new EventMachine.run ... end def stop EventMachine.stop endend

Clusteringless failure faster

out-of-the-box• JBoss provides

• session replication

• load-balanced messaging

• mod_cluster provides

• session affinity

• intelligent load-balanced web

• failover

JBOSS_CONFTorqueBox ships with two JBoss server configurations: default (not clustered) and all (clustered). To enable clustering...

$ export JBOSS_CONF=all

deploy and run

$ export JBOSS_CONF=all$ jruby -S rake torquebox:deploy$ jruby -S rake torquebox:run

mod_cluster

A reverse proxy implemented as an Apache module with JBoss awareness. Constantly gathers load statistics and deployment availability for intelligent request distribution.

mod_cluster

• Dynamic configuration

• Server-side load factor calculation

• Fine-grained web app lifecycle

• AJP (Apache JServ Protocol) is optional. HTTP[S] is also supported.

Futurecoming soon

Future• Performance benchmarking and

optimization

• Infinispan for ActiveSupport::Cache and NoSQL persistence

• JBoss SSO, HASingleton, logging

• CDI injection of Java components into Ruby

• More JavaEE bridged to Ruby where it makes sense, e.g. BPM, Drools, Transactions, etc.

Resources

• http://torquebox.org

• #torquebox on freenode

• https://github.com/torquebox

• http://twitter.com/torquebox

• http://projectodd.org

Thanks!questions?

Crank Up Your Apps With TorqueBox

Documents