Your Azure Architecture Diagrams Explained — Excerpt
Documenting your Azure architecture can be a tedious job. Whether you are building your diagrams by hand (which you shouldn’t) or using an automated Azure documentation generator, understanding the different layers can be difficult.
This article will help you understand each section of a global Azure architecture diagram. The diagram used as our example was generated by Cloudockit and edited in diagrams.net. Keep in mind that depending on the size of your Azure architecture, your diagram could be smaller or bigger than our example.
1 – Load Balancers and Public IPS
Azure Load Balancer enables you to disburse traffic across a group of backend resources and servers. The load balancer allows you to get high availability for your applications.
There are 2 types of load balancers, public or internal (private). The public Azure load balancer provides connections for virtual machines within your virtual network. A private load balancer is used when private IPs are needed solely at the front end.
Public IP addresses enable Internet resources to communicate inbound to Azure resources and for Azure resources to communicate to the internet. However, a resource without an assigned IP address is still able to communicate outbound.
Azure Load Balancer is connected to Azure VM to distribute traffic to the virtual machine. Lastly, Azure public IP connects to Network Interface Cards to allow access to the internet for the resources connected to the Network Interface.
