techno.blog”Dion”: TIBCO on Rails
This is why, for Twitter to scale nicely, it probably makes sense to use a message bus that can scale out nicely. Pull versus Push / the loose coupling can really help you out, and you can copy what NASDAQ does instead of Basecamp.
The message bus could be Ruby, could be ActiveMQ, could be TIBCO Rendezvous.
This architecture change would surely do a lot more for you than “re-write it in Java”, which may give you a slight boost e.g. more out of less machines, but is like adding lanes to 101 instead of using public transport.