<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud Architecture</title><link>https://www.dggcloud.com/en/</link><description>Recent content on Cloud Architecture</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 30 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.dggcloud.com/en/index.xml" rel="self" type="application/rss+xml"/><item><title>Hub-and-spoke across three clouds: Transit Gateway, Virtual WAN and NCC</title><link>https://www.dggcloud.com/en/posts/hub-and-spoke-multicloud/</link><pubDate>Wed, 30 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.dggcloud.com/en/posts/hub-and-spoke-multicloud/</guid><description>&lt;p&gt;Hub-and-spoke is the backbone of almost every landing zone: a central transit point that connects workload networks, on-premises connectivity and traffic inspection. All three providers offer a managed service for it, but their routing models differ.&lt;/p&gt;&#10;&lt;h2 id="the-common-pattern"&gt;The common pattern &lt;a class="anchor" href="#the-common-pattern" aria-hidden="true" tabindex="-1"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;pre class="mermaid"&gt;flowchart LR&#10; OnPrem[On-premises] --- Hub&#10; Hub[Transit hub] --- A[Production spoke]&#10; Hub --- B[Non-production spoke]&#10; Hub --- C[Shared services spoke]&#10; Hub --- FW[Inspection / NVA]&lt;/pre&gt;&#10;&#10;&lt;h2 id="quick-comparison"&gt;Quick comparison &lt;a class="anchor" href="#quick-comparison" aria-hidden="true" tabindex="-1"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;table&gt;&#10;&#9;&lt;thead&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Aspect&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;AWS&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Azure&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;GCP&lt;/th&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/thead&gt;&#10;&#9;&lt;tbody&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Service&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Transit Gateway&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Virtual WAN (hub)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Network Connectivity Center&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Scope&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Regional (inter-region peering)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Regional hub, managed mesh between hubs&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Global hub&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Segmentation&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;TGW route tables&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Virtual hub route tables&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Spoke groups and export filters&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Hybrid connectivity&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Direct Connect, VPN&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;ExpressRoute, VPN&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Interconnect, HA VPN&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;h2 id="creating-it-from-the-cli"&gt;Creating it from the CLI &lt;a class="anchor" href="#creating-it-from-the-cli" aria-hidden="true" tabindex="-1"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;h3 id="aws"&gt;AWS &lt;a class="anchor" href="#aws" aria-hidden="true" tabindex="-1"&gt;#&lt;/a&gt;&lt;/h3&gt;&#10;&lt;p&gt;Disabling default association and propagation forces you to design route tables explicitly, which is what you want when segmenting environments.&lt;/p&gt;</description></item><item><title>Private access to managed services: PrivateLink, Private Endpoint and Private Service Connect</title><link>https://www.dggcloud.com/en/posts/private-access-managed-services/</link><pubDate>Wed, 23 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.dggcloud.com/en/posts/private-access-managed-services/</guid><description>&lt;p&gt;Reaching a managed service (a secrets manager, a key vault or the provider&amp;rsquo;s own APIs) without traversing the Internet is a common requirement in regulated environments. All three providers solve it with a private IP inside your network that fronts the service.&lt;/p&gt;</description></item><item><title>About</title><link>https://www.dggcloud.com/en/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.dggcloud.com/en/about/</guid><description>&lt;p&gt;I&amp;rsquo;m a platform engineer working daily with infrastructure on AWS, Azure and Google Cloud: hybrid networking, landing zones, identity and migrations.&lt;/p&gt;&#10;&lt;p&gt;This blog covers the architecture decisions behind each deployment: what I chose, what I ruled out, and why. Most examples use each provider&amp;rsquo;s CLI and link to the official documentation.&lt;/p&gt;</description></item></channel></rss>