Scout is an extensible server and application monitoring service which focuses upon ease of installation and configuration. Scout offers default alerts to help administrators understand how the application is behaving under various loads as well as allowing developers to create plugins to extend Scout.
This article presents the main takeway points as seen by the many attendees who blogged about QCon. Comments are organized by tracks and sessions: Turotials, Keynotes, Agility as a Craft, Architecture for the Architect, Architectures You've Always Wondered About, Cool Stuff with Java, DSL in Practice, Emerging Languages, The Cloud: Platform or Utility, The Many Facets of Ruby, and many more!
Joern Barthel introduces the Advanced Message Queuing Protocol (AMQP), and illustrates it's useage from a Ruby app with the open source RabbitMQ server on the backend (which is written in Erlang). 1
InfoQ has conducted a virtual panel with people from JIRA, FogBugz, Basecamp and MantisBT about the evolution of bug trackers and the future developments in this field. 3
FlightCaster, a flight delay prediction site, uses Clojure and Hadoop for the statistical analysis, with a Rails/Heroku frontend. We talked to Bradford Cross about Clojure and functional programming. 1
InfoQ's Rob Bazinet and Matthew Bass had the opportunity to talk with Jeremy McAnally, about the book he co-authored with Assaf Arkin, Ruby in Practice.
This book covers intricate details of the Ruby language today, including the latest Ruby 1.9.1, and gives developers a solid foundation for creating Ruby applications.
One of the more interesting announcements recently coming to the Ruby community was the release of JetBrains RubyMine IDE for Ruby and Ruby on Rails applications.
The main takeway points and lessons learned from QCon London 2009 as seen by the many attendees who blogged about QCon. Experience QCon through the opinions of the attendees! 1
Ruby on Rails has done well since its introduction a few years ago, but criticised for not scaling. Developers know there are right and wrong ways to solve problems, scaling Rails is no different.