Hi,

Recently, I built the Azure Solution Architect Map and the Azure Security Architect Map aimed at helping Architects finding their way in Azure. Given the unexpected success and the very positive feedback I received, I decided to come up with other maps, namely the Azure Infrastructure Architect Map and the Azure Application Architect Map.

Here are all the maps in my series of Architecture Maps:



The purpose of the Solution Architect map is to give a high-level view and quick insights about what is available and how to choose between the different services according to some functional needs.

It covers a few key areas, mostly about putting in place the foundations of an Azure Platform, and cannot go into the details because this would make the map very indigestible. The goal of the Azure Security Architect Map is to zoom into security-specific concerns towards Azure.

Today I came up with the Azure Infrastructure Architect Map:

The Infrastructure Architecture Map focuses on the infrastructure only and goes much deeper into that key area. It is by no means the holy grail but it should help you take informed decisions on how you plan to use and deploy services and how you will govern your Azure workloads.

The map focuses on the following areas:

High Availability

Disaster Recovery

Monitoring

Backup & Restore

Network

Infrastructure as Code

How to read this map?

Whenever you see the attachment icon , it means that I have attached an explanation on a given rationale or service. If you see a (*) next to a node, it is kind of a must read information. So for instance, in the following screenshot:

I want to catch your attention on the following:

The rationales behind certain routes are based on my own experience and do not represent the only option but should be considered as advisory only. So the idea is to review these maps frequently since the above information is likely to change over the coming months and I'll simply keep adding notes or remove them when it does not make sense anymore.

The link icon is a pointer to the corresponding Microsoft documentation.

With this tool, any Infrastructure Architect (Cloud or not) will quickly grasp the infrastructure landscape of Azure.

Here is the pointer to the map:

Here are all the maps in my series of Architecture Maps: