Understanding Latency

Latency of 250+ ms

We use Microsoft Azure for all the cloud hosting. A latency of <300ms is well within normal limits at Azure and at par with AWS or Google Cloud. We use AWS as well. Any request to Azure goes through its own layer of WAF (Firewall), Cloud Defender and then Load balancer, who will then forward it to Clinicea’s application server to respond. So even if the Server was hosted right next door to you, it will still take 250+ ms to respond in terms of latency. That is the price we all pay for security and high availability.

However, to the end-user the impact of this latency should not be visible when opening a webpage, in Clinicea. Because we DNS pre-fetch the resources and assets of the web page even before you click. We also cache the DNS pathway locally on the user’s browser for subsequent requests. After the first request, the subsequent requests should not exhibit any impact of latency. Additionally, we do something that most software vendors do not provide i.e,. SPA architecture in a clinic management software. If you notice all the key webpages of clinicea ie Scheduler, Billing, EMR, CRM, Reports, only load once in the entire user session. When you leave the Scheduler to goto Billing and then upon completion of billing, revert back to Scheduler, you will see the Scheduler DOES NOT reload. You just see updated data – you can keep the network panel upon and filter on the Doc panel to see it live. We have a global clientele and knew that latency will pose an issue if we use pure Cloud hosting, and built the framework from Day 1 to overcome that.

While latency will continue to lessen in impact as we make progress - HTTP2 will further reduce impact, it cannot go away as we are limited by the law of physics. You can check the latency of Clinicea against any Azure data center in the world here: https://www.azurespeed.com/Azure/Latency

This is not our website, it’s a general-purpose tool to give comparison. You will find that anything below 250-300ms is on the super-fast side across all of Microsoft Azure’s data centre. Google averages 300ms, AWS is significantly slower starting from 500+ms.

Updated on: 09/06/2023

Was this article helpful?

Share your feedback


Thank you!