Gustavo Brito
Latency test between Azure and On-Premises – Specifications
Internet Connection
Create IT as an Internet connection of 100mbps Down/20mbps Up. Azure was capping at a 150mbps symmetrical connection.
TeamViewer VPN, Azure Site-to-Site and Point-to-Site...
Latency test between Azure and On-Premises – Conclusions
And when all testing’s complete… A final review is coming! So, brace yourselves and let’s start with a graph ?
Note: 5MB results must be...
Latency test between Azure and On-Premises – Part Seven
In this scenario we would be using a Relay. This is yet another way of connecting your on-premises infrastructure to Azure, but not recommended...
Latency test between Azure and On-Premises – Part Six
In this test, we’ll be using Function Apps and Logic Apps. Function Apps are a serverless concept of running custom code in Azure. Serverless...
Latency test between Azure and On-Premises – Part Five
Point-to-site. PTS for now on. PTS is a way of connecting single clients (machines) to a gateway in Azure, without connecting the entire infrastructure...
Latency test between Azure and On-Premises – Part Four
Starting with a real-world application of Azure (it’s used here on Create), this scenario is a direct 24/7 VPN link to a gateway in...
Latency test between Azure and On-Premises – Part Three
This scenario is based by direct HTTP connection via exposed web service, accessible without VPN. This can be a very common situation nowadays too,...
Latency test between Azure and On-Premises – Part Two
In this scenario, we’ll keep it simple. This is the full on-premises scenario. You must worry about maintenance and power bills, and I’m not...
Latency test between Azure and On-Premises – Part One
First test - TeamViewer VPN
In this first test, we are connected via TeamViewer VPN (specification of this technology at the last post) to an...
Latency test between Azure and On-Premises – Intro
In these series of posts, we’re going to compare different ways of connecting to Azure. We’ll setup a web service and a client. We’re...