Comments on: Microblogging is a mess!

By: Alex Leverington

Alex Leverington — Thu, 22 May 2008 06:04:20 +0000

@alex, @curvezilla
I’ve got a plan. A seriously serious plan.

@Jim you can also configure facebook to set your status via twitter.

By: Jim

Jim — Wed, 21 May 2008 16:39:24 +0000

Facebook has a decent “microblogging” application by updating your “status” via a text message.

By: Curvezilla

Curvezilla — Wed, 21 May 2008 03:06:48 +0000

We are in! This deal can only be sealed over sake bombs and sushi.

By: Alexander Muse

Alexander Muse — Wed, 21 May 2008 00:49:45 +0000

Curvezilla - how about we build it together…

By: Curvezilla

Curvezilla — Wed, 21 May 2008 00:26:52 +0000

Big in Japan could build a beefier microblogging app called “Musing”. Do you muse?

By: Alex Leverington

Alex Leverington — Tue, 20 May 2008 23:01:18 +0000

No offense to twitter but, thousands of hits per second is not a lot. Can you imagine how hard the full blogging sites get hit? They are not this unreliable and have just as many people with RSS readers and more complex content.

One solution is separating the HTTP infrastructure between reads and writes and create a node-based distribution system. At the very worst only X number of sites will go down instead of the whole system. Oh yes, this sounds easy in a blog post explanation but I’m sure it’s very difficult and expensive.

By: Fred Oliveira

Fred Oliveira — Tue, 20 May 2008 22:57:49 +0000

I didn’t refresh before typing in my comment, so I missed the two before my own. Apologies. Alex: it is a database issue, no doubt, but I wouldn’t go so far as calling MySQL a bad solution - it’s actually a great solution if used wisely. Just as PostgreSQL with partitioning and slony be another good solution to their problem. It kinda hurts my eyes and ears to see so many people claiming this is a Rails issue when it clearly isn’t - but people are known to throw out hipothesis even if ill-informed.

By: Fred Oliveira

Fred Oliveira — Tue, 20 May 2008 22:52:28 +0000

I’m astounded with the quality of the online software we use these days. Both Twitter and Pownce are tricky applications with quite a lot of users. However, there are solutions to these scaling problems (architectural changes to the apps, better queueing systems, erlang-based implementations) but no sign of them being used, or these problems being tackled.

It’s frustrating, but once you sit on a pile of $, moving becomes a commodity not a necessity for many (unfortunately most) of these products and startups.

By: Alexander Muse

Alexander Muse — Tue, 20 May 2008 22:42:19 +0000

So, we looked into this. I think it is almost 100% a database issue. They are trying to use MySQL and we believe this is their issue. The Obvious folks need to contract (i.e. they don’t need to hire) with a database expert and migrate to a real solution. I suspect we could find someone (or a small team) to get everything stable within 30 days. Perhaps at a cost of $80,000. This isn’t a rails issue…

By: Bradley

Bradley — Tue, 20 May 2008 22:26:51 +0000

I had seen that TC article earlier… I’m guessing the guys over at CakePHP are snickering and chanting “rails can’t scale.” who knows what the real issue is but the microblogmasters better get their act together.

p.s - you gotta watch out for that tabber, it’s not very friendly with big images in posts