Search for a command to run...
I used to be a .NET developer. Nowaways, I am a DevOps solutions architect with a focus on Azure and Kubernetes.
I also love productivity topics, especially when it comes to doing more with less of my time. I'm also a daddy, so time is a limited resource for me.
No comments yet. Be the first to comment.
I'm going to share all my secrets with you
Using a pull-request workflow
This is the guide I wish I had
Connecting your GitHub Workflows to Azure AD using OpenID Connect
In this post, I’ll walk through the essentials of configuring an AKS cluster to use Argo CD with an NGINX Ingress Controller. Pre-Requisites You’ll need: An AKS cluster. Here’s a Gist I use to create a simple cluster. Helm 3 Azure CLI A Custom DNS/A...
This is the first post in a series to try to determine roughly the performance of Azure App Service Hybrid Connections. I’ll create a quick experiment to measure any latency introduced by hybrid connections in comparison to an direct connection and also app service vnet integration.
I anticipate that there is anywhere from 100-500 ms latency added by simply choosing to use Azure App Service Hybrid Connections. I also anticipate that the Azure App Service vnet integration is faster than hybrid connections.
For the experiment, I’ll test three cases. First, I’ll measure the performance of an Azure App Service hosting an API that issues requests to another API. This other API will be hosted on a VM through IIS and listening on port 80. In this case, this other API will be publicly accessible from the internet.
Using a direct connection through internet
Secondly, I’ll measure the performance of the same Azure App Service hosting the API issuing requests to the second API. This other API will remain hosted through IIS on a VM and listening on port 80. In this case, the first API will connect to the second API using hybrid connections.
Using Hybrid Connections
Third, I’ll measure the performance of the App Service connecting to the second API using Azure App Service vnet integration. The second API will not be publicly accessible and instead it will be accessible only through from within the VNet.
Using app service VNet integration
