post

You Can’t Compare Technorati to Amazon

It’s rare that I get into a public debate with a fellow Enterprise Irregular, but today is the day:

Michael Krigsman at ZDNet’s Project Failures cites the stellar response by Technorati as exemplary customer communication at a time of system failure that Amazon should learn from.

True, Amazon did not shine (that’s an understatement) when S3 went down earlier today. I’m sure Amazon will work on not only improving infrastructure, but communication – like Salesforce.com did after their major outage, establishing an Health Monitor, reminds us Lassy Dignan at ZDNet.

True, Technorati was exceptionally forthcoming in that particular incident – but the emphasis is on exceptionally, which is why I would not set them as role model for quite a while. Infrastructure problems have been the constant state of affairs for Technorati for years, the Technorati Monster is still at large, and most of these problems have been swiped under the carpet. In fact when they recently removed old posts from their online index without any notification, they explicitly stated they hoped most users wouldn’t notice.

I salute Technorati on their new approach to transparency, if it holds – but they are very, very far from being a role model.smile_sad

post

The Dawn of SaaS-on-SaaS – Even While Amazon S3 is Down.

TechMeme is great in threading together relevant posts, but is largely based (so I think…) on direct linking, so of course it could not auto-detect the ironic relationship between:

Phil quotes Greg Olsen, CTO of Coghead, a web-based development platform which moved its servers to the Amazon infrastructure recently:

“As ironic as it may be, we continue to see software applications deployed as a service but which fail to use any service-based infrastructure themselves”

“The move to SaaS applications built on SaaS is a much more profound shift than the move from on-premise applications to SaaS applications …”

“Ironically, some of the first victims of this new economy may be some pioneers of the software-as-a-service movement. Today, many established SaaS application providers are applying much more of their precious focus and capital to infrastructure issues than newer competitors that are aggressively utilizing service-based infrastructure … the build-it-all-ourselves SaaS application vendor … will ultimately end up as [an] anachronism.”

Today’s Amazon outage appears to rebuff Phil and Greg’s point. Reality check: this is the first time Amazon S3 went down, and it’s already back up. Salesforce.com had its fair share of outages, so did other SaaS providers, and so did just about any in-house systems companies run their own installed software on. I’m a big believer in focus, specialization and I trust the few mega-cloud companies that will emerge can maintain a more robust infrastructure than we could all do individually. (So yes, if it’s not obvious, I do buy into Nick Carr’s Big Switch concept.)

Another approach is to look at where value can be added: the consensus view from a quick Enterprise Irregulars chat is that infrastructure will be commoditized faster (or it already is) than software, where there is a lot more room for innovation by new and – thanks to outsourced infrastructure – smaller players.

And if acronyms were not ugly enough already, here’s to entering the age of SaaS-on-SaaS. smile_shades

Update: What better confirmation of my point than today’s rumors about EMC hosting  SAP’s system  – I assume it’s Business ByDesign, the new On-Demand offering for the SMB market. (Side-note: I’ll be traveling and be time and Internet-challenged for the next three weeks, but SAP’s BDD is one of the subjects I will come back, as it seems to be largely misunderstood. Oh, and I just love the fact how Mozy, my favorite online backup service is often referred to in the EMC story).

 

Related posts (on the Amazon outage): Rough Type, mathewingram.com/work, LinkFog, Data Center Knowledge, Web Worker Daily, TechCrunch, Moonwatcher, Project Failures, SmoothSpan Blog, Enterprise Anti-Matter.