THE QUEST FOR WHIZZ-BANG-WOW-SUPER-FAST REAL TIME!

I read with interest a recent press release from a technology provider announcing WHIZZ-BANG-WOW-SUPER-FAST millisecond response times for performance benchmark tests for real time fraud prevention, which naturally caused me to dig into our own benchmark test archives a while back to make the obvious technological comparisons......not the purpose of this article.

It got me thinking to what happens in real business situations..

TPS (transactions per second) and ms (millisecond) response times are all very well, but the fraud, risk, or security manager fully expects (when online, real-time is required) that their own organisation's performance testing will be able to handle whatever the client will care to throw at the vendor's technology.

Any technology project would surely encompass (and typically mandates) a decent element of performance testing before going into any production environment.

So with fraud prevention and security vulnerabilities, I've typically found it's the organisation's people that typically require the millisecond response times to implement a new rule, invoke a patch, or simply to get a project underway and completed.

Of course, I'm not dismissing the need for speed, but if you're looking up an incorrect database entry very very quickly it's not going to impress anyone at the end of the day!

(REFER Database glitches affect payments to Egg)

As the 80's classic suggests..."It Ain't What You Do It's The Way That You Do It".