So for instance, in the following screenshot: If you see a (*) next to a node, it is kind of a must read information. Whenever you see the attachment icon, it means that I have attached an explanation on a given rationale or service. Miscellaneous: things that come back regularly when developing applications such as real-time HTTP, search, job scheduling etc.Artificial Intelligence: NLP, Supervised & Unsupervised ML etc.Domain-driven Design & Microservices: yes I clubbed them together :).Common Design Patterns: SAGA, Circuit Breaker, Event-driven Architecture, etc.My goal is only to highlight some possibilities.Īs usual, here is a screenshot of the map: This map is certainly subject to controversy as they are thousands of ways to design and develop and application. I'm now coming with the next map in this series, namely: the Cloud-native Azure Application Architect Map.Īs 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. The Cloud-native Azure Application Architect Map - This map.The Azure Kubernetes Service (AKS) Architecture Map.The OpenID Connect (OIDC) Architecture Map.
ARCHITECT AZURE SERIES
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: