What Do SAP Consultants Think HANA Zero Latency Means?

Executive Summary

  • 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

Our Response

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.

The Necessity of Fact Checking

We ask a question that anyone working in enterprise software should ask.

Should decisions be made based on sales information from 100% financially biased parties like consulting firms, IT analysts, and vendors to companies that do not specialize in fact-checking?

If the answer is “No,” then perhaps there should be a change to the present approach to IT decision making.

In a market where inaccurate information is commonplace, our conclusion from our research is that software project problems and failures correlate to a lack of fact checking of the claims made by vendors and consulting firms. If you are worried that you don’t have the real story from your current sources, we offer the solution.

Financial Disclosure

Financial Bias Disclosure

Neither this article nor any other article on the Brightwork website is paid for by a software vendor, including Oracle, SAP or their competitors. As part of our commitment to publishing independent, unbiased research; no paid media placements, commissions or incentives of any nature are allowed.

S/4HANA Implementation Research

We offer the most accurate and detailed research into S/4HANA and its implementation history. It is information not available anywhere else and is critical correctly interpreting S/4HANA, as well as moderating against massive amounts of inaccurate information pushed by SAP and their financially biased consulting ecosystem.

Select the description that best matches you.

Option #1: Do You Work in Sales for a Vendor?

See this link for an explanation to sales teams.

Option #2: Do You Work for an Investment Entity that Covers SAP?

See this link for an explanation for investment entities. 

Option #3: Are You a Buyer Evaluating S/4HANA?

For companies evaluating S/4HANA for purchase. See this link for an explanation to software buyers

Search our Other In Memory Computing Content