Joshua Ballanco introduces Immutant, Immutant Overlay, HornetQ and OpenShift to Ruby and Rails developers.
Jim Weirich attempts to lure developers to use Ruby for their daily programming tasks.
Gareth Rushgrove overviews Ruby on Rails and Django: object caches, fragment and HTTP caching, asset compilation, profiling, log file measurement and framework hooks for instrumentation.
Jamie Wright introduces some of the tools, libraries, and methods used to build a SaaS system in Ruby on Rails.
Brian Ketelsen introduces Skynet, a platform for polyglot, distributed and composable services that communicate with each other over RPC/JSON.
Jesper Richter-Reichhelm shares the lessons learned while scaling their game platforms to handle millions of users, each game being built by small teams of two developers without dedicated ops.
John Davies examines Visa’s architecture and shows how major enterprises have architected very complex integrations incorporating Hadoop, memcached, Ruby on Rails, and many others to deliver innovative technology solutions. John explains how the platform architecture and technologies -- integrated and invented -- must be reliable and able to massively scale.
Sarah Allen talks on how to introduce children to the basics of programming, presenting a new related language called “Pie” along with lessons learned from creating a DSL in Ruby.
Jeff Cohen advises on how to switch from another language to Ruby and how to integrate it into the enterprise, presenting what are Ruby’s core elements and 5 myths about Ruby and Rails.
Get Satisfaction Uses Ruby on Rails and Cloud Computing Platform to Achieve Scalability and Reliability
Thor Muller presents how Get Satisfaction managed to reliably scale their Ruby on Rails-based customer community platform using Agile, TDD, BDD, and by deploying their framework in the cloud.
Yehuda Katz presents the evolution of the Ruby on Rails project, the challenges it had to overcome and what are the lessons that could be helpful in making other open source projects successful.
Neal Ford shows what ThoughtWorks learned from scaling Rails development: infrastructure, testing, messaging, optimization, performance.