Scenario: You are finally convinced that Ruby on Rails is a great platform for building web applications, and so you try it out and build this awesome new website in only 3 weeks of development. You launch version 0.99 beta and everyone thinks it’s cool. Maybe it’s something like Insoshi, or Twitter. (Insoshi is hot new social networking platform (FOSS) written in Ruby on Rails (RoR). Yes, they eat their own dog food.)
Scene 2: TechCrunch posts an article telling the world about your cool RoR Open Source Social Networking stuff. This is great free publicity, but can your application handle the TechCrunch effect? Will your RoR Social Networking application be able to handle the spike in traffic? Can you handle the success of becoming a very popular new application? (Rumor mill… Twitter is having scaling problems… said to be abandoning Ruby on Rails. However DHH, the master architect of RoR, joined Twitter as D2H on 29-Apr-2008, and instantly had over 1200 followers.)
Scene 3: Slashdot comes back online after being down for 5 hours, and someone posts an article about your hot beta site — sez its cool. Will it suffer from the Slashdot effect? How will your application perform under peak load? Does it scale up to handle thousands or millions of hits per hour?
Scene 4: You can’t handle the TechCrunch effect and Slashdot effect all on the same day. Your web site crashes and burns. Your dream, website, and reputation is ruined — all in one day.
The video is kind of funny, and does reveal some tidbits of truth about the complexity of enterprise java development. But those who have been reading about Ruby and JRuby for a while realize that you can run Ruby and Ruby On Rails with Java.
But if you think about it… guess that goes to show you there’s a-lotta-truth here.
November 20, 2007
at 5:56 am
· Filed under Webdesignology
This one (Mongrel onepointonepointone ) is just a little bug fix, fixing the Mongrel 1.1 mongrel_rails restart bug. Mongrel is a web server, that is cooler than a brick, and if you have used TomCat in the past, or heard of TomCat, you might understand the inside joke (TomCat vs. Mongrel (Dog)).
Most of the cool people who understand this stuff (wink, wink), are letting the cat out of the bag, because a dog is man’s best friend. But this really not really not a cat-fight, or even Cat vs. Dog fight, since even the guy who wrote TomCat has switched to Mongrel.
November 2, 2007
at 6:30 am
· Filed under Technology
Mongrel 1.1 is out, with JRuby support. Mongrel_cluster is also updated to 1.0.4, with fixes for a Capistrano recipe bug. More excitement and more power …
He lists 10 reasons to love Ruby on Rails. The first reason really resonated with me since I’m a systems architect, and I understand the dangers of over-architecting solutions
“1. Many line-of-business applications do not require over-architected, complex and costly software systems to operate. Over-engineering applications increases costs, wastes time and dilutes competitive advantage. Rapidly-constructed software applications that deliver essential functionality with good scalability and low maintenance costs are easily achievable using Ruby and the RoR framework.”
