Cloud Archive Solution
Archives: Projects
Azure DNS Design (HLD)
DNS was, and it plays a significant role on-prem for simple naming translation to IP and finding services like Identity Provider and so on, but with cloud computing, it has an even more substantial role to play internal DNS, Service Provider DNS, and public DNS all could get involved in a single process
Managed From and Managed to Infrastructure
Human Capital Management (HCM)
Another graphic representation of a product in this case Oracle HCM.
This information could be well presented in a table but an infographic is always easier to follow.
M365 Security
This infographic was part of a presentation related to Microsoft 365 and received excellent feedback, but it may not be technically correct today as it was for early 2020
Azure Network Diagram (HLD)
Infrastructure Infographics
These are two old Diagrams that I optimized for sharing on the web, but they have been successfully tested for presenting to high-level management as well as engineers
SFTP for Azure
another infographic design for an SFTP service in Azure
Azure does not have SFTP as a Service, but we could easily create an ARM template to build Container Instances using Azure Storage file share for the storage
Business Domain Architecture (from technology point of view)
Business Domain Architecture
Business Domain Architecture (BDA) is a combination of Departments/ORG Charts and Traffic/Data Flow diagrams
BDA always helps me to understand how the Business works but, most importantly, allow me to simplify designs and decisions
Note: BDA is different from Business Application, Data and Security Architecture, but in my opinion, you can not provide that architecture without DBA
I will create a BDA Diagram for this post, so it is entirely made-up Business instead of using one of my actual diagrams, but it demonstrates the points
let’s say the company is called ParsCorp, and it has IT, HR, Finance, Marketing, customer service, CEO/Bord, Risk and Factory
ParsCorp assembles TV and Monitors and has 2 physical locations, HQ and Factory
the first step is to create a diagram that shows different departments in the company and if they have any teams inside them
in this case, I focused on the IT department and created a complete subitems category
this could help to identify the capability map related to each department or domain
now let’s focus on the IT domain and find out what functionality IT need to provide for this company to run (we could create a diagram that shows current capabilities or minimum capabilities)
Diagram 1 shows the power of an IT department for a small company, and Diagram 2 offers a larger company with could footprint
Datacentre Design
Datacenter Network Design
In this post, I will try to show the power of a clear and straightforward diagram for building and troubleshooting a complex datacentre
This project was for one of the most significant IT projects in Australasia, but here I want to talk about a small project, the physical Networking for one of the data centres.
Note: This project is almost eight years old, and all the names and configs in these diagrams have been replaced
Technical Requirements
- The solution MUST support IPV6
- The solution MUST support a multitenant environment
- The solution MUST support SDWAN
- The solution MUST provide tenant and customer separation
- The solution MUST support SDN
- The solution MUST support scale-up and scale-out
Solution
- Any one of the big brands would support IPV6
- v-Routers, v-Firewalls and vLAN will be used
- Any one of big brands would support SDWAN
- Managed to and Managed from design
- Any one of the big brands would support SDN
- any clustering will provide the solution
Physical Connectivity
In this diagram, you have all the physical locations (e.g. rack number), name of the device, functionality and IP address to connect to the device
since it is not a rack design, so you do not have the exact location in the rack, but instead, you have all the physical connectivity, speeds and identical port number, including connectivity to other infrastructures
having the port numbers in this diagram was handy as I could request a configuration on the exact port without searching a spreadsheet for the correct port number
The logical diagram presents a multi-tenanted multi-datacentre solution.
Building Block Architecture (BBA) patterns are everywhere in this design for instance; every tenant has the same component LB/Router, the same connectivity to the tools and internet, which would help for automation and simplify the troubleshooting
at this stage, we could imagine a new customer and see how this pattern could be applied to the solution
The Architecture Blog 
You must be logged in to post a comment.