The Cloud-native Azure Application Architect Map

This article is contributed. See the original author and article here.

Hi,

 

Recently, I built the Azure Solution Architect Map , the Azure Security Architect Map  and the Azure Infrastructure Architect Map aimed at helping Architects finding their way in Azure. Here are all the maps in my series of Architecture Maps:

• The OpenID Connect (OIDC) Architecture Map


• The Azure Kubernetes Service (AKS) Architecture Map


• The Cloud-native Azure Application Architect Map – This map


• The Azure Infrastructure Architect Map


• The Azure Security Architect Map


• The Azure Solution Architect Map

 

I’m now coming with the next map in this series, namely: the Cloud-native Azure Application Architect Map.

As usual, this map is by no means the holy grail and is just there to highlight some good fit between Azure Services and Design Patterns. This map is certainly subject to controversy as they are thousands of ways to design and develop and application. My goal is only to highlight some possibilities.  

 

As usual, here is a screenshot of the map:

 

 

The map focuses on the following areas:

• Data & Big Data


• Common Design Patterns: SAGA, Circuit Breaker, Event-driven Architecture, etc.


• Domain-driven Design & Microservices: yes I clubbed them together :)


• Artificial Intelligence: NLP, Supervised & Unsupervised ML etc.


• Miscellaneous: things that come back regularly when developing applications such as real-time HTTP, search, job scheduling etc. 

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 why I make an association between DDD and Microservices:

as well as why I make an association between CQRS and DDD:

You might of course disagree with this but at least, you understand my rationale.

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

 

Note that I haven’t dived into AKS or Service Fabric since this guys would deserve a dedicated map and are not Azure services like others, they are a universe by themselves.

 

With this tool, any Cloud-native Application Architect should quickly grasp the application landscape of Azure. 

 

Update: the online MindMapMaker tool deletes maps that are older than a year, therefore, just visit the last version.

v1.0 & v.1 (09/2019)	https://app.mindmapmaker.org/#m:mm5e724c4dc8324504ab58c6d9b0f708b8
v 1.2 (12/2019)	https://app.mindmapmaker.org/#m:mm41003e37953d47e0841ae28cf0079f0e
Last version MindMapMaker	https://app.mindmapmaker.org/#m:mm87db50f890484619b2429b32c3545916
Last version PDF	https://github.com/PacktPublishing/The-Azure-Cloud-Native-Architecture-Mapbook/blob/master/Chapter05/maps/Azure%20Application%20Architecture.pdf

 

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

• The OpenID Connect (OIDC) Architecture Map


• The Azure Kubernetes Service (AKS) Architecture Map


• The Cloud-native Azure Application Architect Map – This map


• The Azure Infrastructure Architect Map


• The Azure Security Architect Map


• The Azure Solution Architect Map

 

 

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.