- In an effort to contradict our research conclusions on SAP HANA, one SAP resource attempted to redefine the term latency.
- What happened after this SAP consultant was questioned on this point?
SAP resources are desperate to undermine Brightwork Research & Analysis. And they come up with creative ways to undermine our conclusions. This is one such misguided example.
Mohamed Judi Quotation on the Definition of Zero Latency
“Let me give you a couple of examples why I can’t take you and your organization very seriously: 1. You have completely misunderstood the term “zero-latency”. It seems due to your lack of knowledge and your predetermined intentions to slander SAP, you understood that “zero-latency.” For your own benefit, “zero-latency” is referred to the fact that there is no need to move data for reporting. The same data that end users save in S/4 will be used for reporting. No latency in moving data is needed anymore. It is not the time that the user is expecting for his/her request to be executed by the platform. Any junior practitioner with little knowledge in networking and databases would have understood it correctly.” – Mohamed Judi
“Well apparently PC Mag is incorrect also. Here is their defintion. “Definition of: zero latency (1) Having no delay between the time a request is initiated and the response is given. See latency.
Hmmmm….that seems to contradict your explanation. Secondly it is entirely obvious from the context that Hasso meant the PC Mag definition. You appear to have created a new definition of latency for yourself. Also notice SAP’s use of the term. “Access real-time operational and strategic insights with near-zero latency.” They switched it to “near-zero” because “zero” was too idiotic and they were getting laughed at for it. I will accept your apology on this. Please offer it in the next response. “
Mohamed Judi did not offer a response.
SAP consultants like Mohamed Judi will tell any lie to try to prop up SAP. This is why fact checking is so important.