Tervela Message Medium Blog

Marc recently had a very good post on his Magmasystems Blog regarding a recent announcement by a legacy messaging vendor that they were entering the hardware game. As a hardware vendor in the messaging space, we welcome the market validation but we have several questions:

Should this legacy messaging be hardware accelerated?

It’s not about messaging; it’s about a messaging architecture that supports acceleration. More lessons here, this time from the automobile world. Shelby SuperCars introduced a 1,183 hp rocket last year that hit 257.41 mph on the road. It wasn’t just about the engine, though. The rest of the car was architecturally matched to it. Putting that engine in the classic Toyota Camry could produce much different – and possibly dangerous - results. You be the judge.

Will this make other problems go away, too?

Again, it’s about architecture. Nothing like a slow messaging consumer to bring down a peer-to-peer framework – even one that’s hardware accelerated. You need a new architecture to fix this. Period.

What about all this XML stuff?

I’ll answer with a question: How prevalent is XML in the high-performance world? Before anyone barks – I’m an XML fan – but for the right applications.

Welcome to the high performance world of hardware. May your engine bolts be fastened properly and your drive train sufficiently matched.

=rob.ciampa

Tags: hardware-based messaging (1) tibco (1) xml (1) shelby supercars (1) 

Comments (0)