This post originated from an RSS feed registered with Ruby Buzz
by Obie Fernandez.
Original Post: Oh the Sanity!
Feed Title: Obie On Rails (Has It Been 9 Years Already?)
Feed URL: http://jroller.com/obie/feed/entries/rss
Feed Description: Obie Fernandez talks about life as a technologist, mostly as ramblings about software development and consulting. Nowadays it's pretty much all about Ruby and Ruby on Rails.
A few days ago I suggested that a certain shop that prototypes in Rails and then rewrites in Java should just go ahead and scale the Rails version. Really, I didn't put much thought into that post at all. I found the quote humorous and figured it might spur some interesting Java vs. Ruby polemics. Furthermore, my comment about firing the Java guys was purely rhetorical -- I don't know any of them and I'm sorry if anyone's feelings were hurt. One of those Java guys, Josh Lucas, was cool enough to post a comment here and then followup on his own blog with additional information about the situation that I believe merits quoting:
(Bold mine)
Yes, we are definitely using Rails to prototype new ideas and more than likely we'll rebuild them in Java but that isn't set in stone. I think the majority of folks on the team would be very interested in launching their Rails code into production. The problem is that I haven't seen any Rails apps which face the level of traffic we would be sending it. Are there any in production having greater than 5 million page views a day? If so, I would love to know about them.
Fair enough. The question is put out there. Anyone serving up greater than 5 million pageviews/day with Rails? It's a legitimate question. Further proving that they really aren't insane at all, Josh adds...
Doesn't it make sense that if these Java guys are prototyping in Rails that maybe there is more to them than just following whatever Java framework is hot.
Yes Josh, it certainly does seem there is more to you guys than following whatever Java framework is hot and I apologize for implying otherwise. Yours might be one of the cases where Rails is not an appropriate architectural choice due to the scaleability concerns OR the Rails community is not doing a good enough job of explaining why it CAN scale to those levels.