Blog vs. Blog: Daring Fireball/GigaOm MobileMe-nia!
Om Malik says Apple is clueless about scaling MobileMe:
There is no-unified IT plan vis-a-vis applications; each has their own set of servers, IT practices and release scenarios. Developers do testing, load testing and infrastructure planning, all of which is implemented by someone else. There’s no unified monitoring system. They use Oracle on Sun servers for the databases and everything has its own SAN storage. They do not use active Oracle RAC; it is all single-instance, on one box, with a secondary failover. Apparently they are putting web servers and app servers on the same machines, which causes performance problems.
John Gruber retorts, with the US' #1 online music retailer firmly in his corner:
But the iTunes Store does gangbuster traffic and has a terrific track record for uptime. The message I read from yesterday’s reorg that put MobileMe under Eddy Cue (Apple’s VP for iTunes) is that MobileMe could and should be as responsive and reliable as the iTunes Store.
The crazy thing is, MobileMe should have been an iTunes-learned breeze for Apple in terms of meeting service levels, given their pedigree. But then iTunes uses WebObjects (which I believe is old school Java-based) and MobileMe uses SproutCore (which is all dressed up in Ajax-y 2.0 objectivity), and the pretty much disastrous July 11th launch, which took down both iTunes iPhone activation, and slammed the MobileMe servers into weeks of problems, show something clearly is different with the new kit on the block.
Hopefully Cue will bring some of the iTunes luster to MobileMe, but only time will tell. What do you think? Which blog wins this round?