Version: 2008
  • On CHOW: Can girls use the guys' bathroom?

Comments on: Scaling Twitter redux--the ESB should be your best friend

Scaling a message-based system is a common enterprise problem. Web 2.0 needs to get a little enterprise-like to make things work better.

Add a Comment (Log in or register) (3 Comments)
  • prev
  • 1
  • next
by Perfeng May 23, 2008 6:54 AM PDT
Sorry, but you really need to not make things up if you want to come across as knowing what you're talking about. OpSource is NOT handling billions of transactions a day using Mule. Yes, their bus uses Mule, and yes, they serve lots of transactions a day, but not every request over the OpSource network flows through the bus. In fact, a very very tiny percentage of them do, and they're not serving billions a day at any rate.

This is not to say that OpSource couldn't help Twitter, I'm sure they could. But it would not involve their ESB, and their ESB is not magic.

Also, JMS is not magic. As a performance engineer, I'm as big a fan of reading about Twitter's problems as the next guy, but the scaling problem they have would be hard to solve on ANY platform. They're going to have to relax some of their requirements, and move to a more asynchronous model to scale. JMS could help them do that, but they could also do it without JMS.

Mule also isn't magic. Unless you've load-tested Mule with millions of messages an hour, involving tens of thousands of queues, some small percentage of which should have thousands of subscribers, you haven't even done an order of magnitude simulation of the Twitter problem. I'm pretty sure Mule would have issues serving Twitter too, and it would take less than a day to implement the basic model and find out, provided you have the machines on hand to handle this load, and sufficient load generation capability. But I'm guessing you don't have either, so maybe OpSource can help you with *your* problem.
Reply to this comment
by shmooth2 May 23, 2008 9:15 AM PDT
@perfeng: dude - take a chill pill. seriously. take a week off. just do something to take the edge off. i'm sorry you got canned from your last position, but it's not cnet's fault. you should have used Mule.
Reply to this comment
by syerramreddy May 24, 2008 4:33 PM PDT
I am not sure if ESB solution will prevent every website outage issues.. I hope it is that simple, I agree with the fundamental view that ESB/Messaging can relieve some load issues, but a blanket recommendation or view that ESB would have prevented the outage is kind of parochial and lacks intellectual assessment..
Reply to this comment
(3 Comments)
  • prev
  • 1
  • next
advertisement

Google's mobile hopes go beyond Nexus One

The world may have thrilled to the potential for a Google Phone, but what Google actually unveiled is its plan for a new smartphone world order.
• Photos: Unboxing Nexus One

Using your smartphone safely

faq Worms, Trojans, and SMS attacks are risks for mobile phones, but the biggest practical threat to users is losing the device.

About Software, Interrupted

In "Software, Interrupted," Dave Rosenberg discusses disruption in the software market, as well as the products and services that keep business technology norms in perpetual flux.

With nearly 15 years of technology and marketing experience spanning from Bell Labs to multiple start-up IPOs, Dave co-founded open-source software company MuleSource and now serves as general manager of Hardy Way. He also happens to be a U.S. patent holder and a workaholic. Technology is his best friend and mortal enemy.

Add this feed to your online news reader

Software, Interrupted topics

advertisement
advertisement