it's the latest twitter-like. the Force is strong with this one...
I was told to say hi to you, but I would also like to add a hearty, How YOU doin'? as well.
didn't see that Plurk had crashed - when did that happen
plurk had some features go offline as they worked on them (auto update) but the service was up
martinbogo I think from the user perspective it's irrelevant if the service disappears accidentally or intentionally, point is: not working
ah, but it -was- working
Only automatic reload (a convenience) was offline. My reload key did get a workout
Twitter, on the other hand, has gone completely offline for hours on end
yes.. I hope when Plurk reaches 1.7 million users, it will hold up better than twitter
MOST sites that have that many people, work better than Twitter
amazon, google, slashdot, techcrunch, sourceforge, digg, reddit,
yes, and which one of those is a chat system?
just curious. yes, but alllllll the ships can carry more than 100 people! Why can't WW do the same???
twitter has an architecture which was designed for completely different goals
that's a big problem. actually, amazon's architecture would not be good for doing twitter like stuff either
Despil :
Amazon.com initial design wasn't made to accomodate these loads either, neither was eBay, or Slashdot
The fact of the matter is, they were able to keep up, plan ahead, and rebuild.
also refutes your initial hypothesis. Twitter's designers -did- want Twitter to handle these loads, and planned poorly.
martinbogo Actually twitter's designer said: we did not except it will be use in this way but this many people.
Ebay, for example, handles millons of transactions per minute.. but even in it's infancy, it had to handle close to one hundred thousand/min
Despil, it doesn't excuse Twitter's horrible management of the scaling issues.
but the fact is, the architecture of twitter is not good for this
I did not say it is an excuse
I scaled Slashdot, Freshmeat, SourceForge .. worked on scaling EverQuest, and consulted with Blizzard on WoW
the fact that the doctor accidentally cut the patient in half with a chainsaw does not change the fact that the patient is cut in half
The fact stands that they have -every- resource they need to scale, and have failed to do so due to poor planning, bad communication
it does not mean the doctor is not faulty. but the patient is dead with the reason of being cut in half
and yes, Twitter is not up to the task. Hope plurk will be
That's just it. They have all the bandwidth and server resources they need. It's plain
stubborness (software architecture philosophy) and crap-poor resource management that's killing them
maybe you should go and help them. for money of course.
They refused the help, even when offered at a reduced rate.
but currently the guy who scaled google maps is failing.
Many of the -best- engineers at scaling issues, have offered to help, some of them gratis.
then they will die which is a pity, but when management makes that kind of mistake, they deserve it
Twitter will be the first, the experiment, and the next one and the one after that hopefully will learn from the mistakes
"indeed," and there is no apology or excuse for their current batch of failure.
wonders what's behind the stage.
sometimes the developers and the technical stuff could bring up the brightest ideas, and the marketing, sales, and management kill off those
we will see. just too many friends over there