I recently started to build several Azure Maps to help architects find their way in Azure. Here is my complete series of Architecture Maps:
AKS is not a service quite like others, so it certainly deserves its own map.
As usual, this map is by no way the holy grail and is just there to highlight some key areas to look at when starting an AKS journey. Several aspects depicted in this map have to be tackled right from the start...With AKS, more than any other service, it is important to think about the broader picture, meaning the other Azure Services you might be using. Should you go 100% the open source way or should you prefer a unified way of managing resources using the Azure ecosystem? Should you prefer a best of suite or a best of breed? The map does not answer those questions but shows different possible routes to achieve similar functionalities.
As usual, here is a screenshot of the map:
The map focuses on the following areas:
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 this icon next to a node, it means that I have attached a must-read information.
The link icon is a pointer to the corresponding documentation.
With this tool, any Cloud-native Application Architect should quickly grasp the AKS universe and how this managed Kubernetes integrates with other Azure Services.
Here is the pointer to the map:
Here are all my Architecture Maps:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.