Hybrid & Multi-Cloud
Provider-neutral by design.
Model AWS, Azure, GCP, on-premises and the connectivity between them as one solution - with trust boundaries and data residency made explicit rather than assumed.
Reference architecture
A realistic hybrid topology - connectivity included.
Enterprise data and identity on one provider, AI and data workloads on another, joined by explicit, realistic connectivity.
Client / Azure
AWS
Note: AWS Transit Gateway does not itself connect to Azure. Real hybrid connectivity uses appropriate mechanisms - site-to-site VPN, Direct Connect / ExpressRoute with partner interconnect, or equivalent - modeled explicitly in the solution.
On connectivity: an AWS Transit Gateway centralizes connectivity within AWS. Reaching Azure or on-premises networks requires an appropriate hybrid link - site-to-site VPN, AWS Direct Connect, Azure ExpressRoute or equivalent. The reference model treats that hybrid link as its own critical component, not an attribute of the Transit Gateway.
Provider strategy
Compare provider-centric and hybrid options.
The same logical solution can map to different providers - with trade-offs made visible.
Option A
AWS-centric
- Complexity
- Medium
- Cost
- $
- Flexibility
- High
Option B
Azure-centric
- Complexity
- Low
- Cost
- $$
- Integration
- High
Option C
Hybrid
- Complexity
- High
- Cost
- $$$
- Data Sovereignty
- High
There is rarely one correct architecture. The platform makes trade-offs explicit so the decision - and its reasoning - is recorded, not assumed.