9 min read

Learning Objectives

By the end of this module, you will be able to:

  • Describe the canonical layered shape: public Layer 7 balancer, stateless compute tier, private Layer 4 balancer, private-only data tier
  • Justify each layer boundary in terms of exposure, traffic type and failure behaviour
  • Place containers, dedicated VMware, AI services and hybrid connectivity onto the layered shape
  • Evaluate a proposed layout against the private-by-default principle

Unit 1.2: The Canonical Layered Architecture

Introduction

Most enterprise designs on IONOS CLOUD converge on one shape. Traffic enters through a public Layer 7 load balancer, reaches a stateless compute tier, passes a private Layer 4 load balancer, and ends at a data tier that has no internet path at all. The shape is not a convention for its own sake. It follows directly from how LANs, load balancers and filtering work on the platform.

This unit explains why each layer exists, where the other product families attach, and how the shape grows as later modules fill it in. You will see this diagram again in every module, with one more part decided each time.

1. The Four Layers and Why Each Exists

1.1 Private Until Connected: the LAN Rule

A LAN in a VDC is either private, without direct internet access, or public, connected to the internet. In the DCD, a network without a connected internet access element is private. When you drag the internet icon onto an existing configuration, the private LAN becomes a public LAN, and that conversion also turns all its private IP addresses into public IP addresses.

That rule is the foundation of the layout. Exposure is a property of the LAN, so you control exposure by deciding which LAN each resource joins. IONOS CLOUD security best practice points the same way: not every VM needs a connection to the public network, and you create security by moving VMs into separate LANs so that only the required applications exchange data. A three-tier layout of a public edge LAN, a private application LAN and a private data LAN is the direct expression of that guidance.

1.2 Layer 1: The Public Layer 7 Edge

The Managed Application Load Balancer (ALB) operates at Layer 7 and supports HTTP and HTTPS. It is used in two ways. As a public balancer, its listener accepts client connections from the internet and the ALB acts as an edge device for north-south traffic; a public listener requires a reserved public IP address. As a private balancer, its listener sits on a private network and handles east-west traffic inside the data center, with no IP input required for the primary listener address.

At the edge, the ALB earns its place through content-aware routing. Forwarding rules can route on header, path, query, method, host, cookie or source IP, and the ALB supports TLS offloading. The edge is therefore where TLS ends and where requests are steered to the right target group. One constraint shapes the tier behind it: the ALB does not support Source NAT (SNAT), so targets cannot initiate connections through the load balancer. Outbound traffic from the compute tier needs its own path (Section 2.2).

1.3 Layer 2: The Stateless Compute Tier

Behind the edge sits the compute tier on a private LAN: Compute Engine servers, Cubes, or replicas managed by VM Auto Scaling. The tier must be stateless, because any instance behind the balancer may receive any request and instances are added and removed. Session state and cached data move to the data tier (Units 4.3 and 5.5).

1.4 Layer 3: The Private Layer 4 Balancer

The Managed Network Load Balancer (NLB) is a Layer 4 TCP balancer. It is a proxy: client connections terminate at the balancer and map 1:1 to connections that the balancer initiates to targets. This is called two-arm load balancing, with one interface facing clients and one facing targets. The NLB listener can take a private primary IP address, so the balancer can sit entirely inside the VDC.

The selection rule is plain: use the ALB when your balancing logic needs to process HTTP requests and their attributes; when routing performance is critical, limit the logic to Layer 4 and route TCP traffic with the NLB. Between the compute tier and the data tier, you rarely need HTTP awareness. You need a stable private endpoint, health checks and distribution across healthy targets. Like the ALB, the NLB does not support SNAT, so targets cannot initiate connections through it.

1.5 Layer 4: The Private-Only Data Tier

The data tier holds the managed data services on a private LAN with no internet access element. A DBaaS for PostgreSQL cluster, for example, is connected to a VDC LAN and given a private IP address from that LAN when you configure its network. Event Streams for Apache Kafka clusters are provisioned inside a VDC and must be connected to a LAN, through which VMs in a private LAN access the cluster.

Filtering reinforces the topology but does not replace it. Network Security Groups attach to VMs and NICs. The NIC-based Firewall, once activated, blocks all incoming traffic by default and passes only explicitly enabled ports. Both protect server NICs. The managed balancers and managed data services are not VMs or NICs that you attach these controls to, so the safe default for the data tier is a LAN that has no public path in the first place.

2. Where the Other Families Attach

2.1 Attachment Points

The following table places the remaining families onto the layered shape.

Family Attachment point Design consequence
Managed Kubernetes Node pools in the compute tier A Service of type LoadBalancer does not provision an external load balancer; the platform assigns a static public IP address as a secondary IP to one worker node, which then acts as the ingress node. Put an in-cluster ingress controller behind it, and front it with the ALB where you need managed Layer 7 routing (Units 6.1 and 6.2).
Private Cloud (dedicated VMware) Beside the VDC, managed through the vSphere Client and NSX-T Manager Its IPSec VPN service supports single or multiple IPSec connections to other endpoints, so it joins the layered shape as a connected site, not as a tier inside the VDC (Units 4.4 and 7.4).
AI Model Hub An endpoint the compute tier calls Inference runs in Germany behind an OpenAI-compatible API that is reachable over the public internet; a private compute tier needs an egress path to call it (Unit 6.5).
Hybrid connectivity The edge of the private LANs VPN Gateway supports IPSec and WireGuard, with IKEv2 for IPSec. Cross Connect joins VDCs in the same contract and region over private LANs (Unit 3.6).
IONOS Cloud Object Storage An endpoint used by every tier Archive, backup target, artifact and dataset store (Unit 5.2).

As shown above, nothing in this list requires a fifth tier. Each family attaches either inside an existing layer or as a connected endpoint or site.

2.2 The Egress Path

Private tiers still need outbound access for patches, external APIs and AI inference calls. The Managed NAT Gateway provides it. It is SNAT-only: it does not support Destination NAT (DNAT), so it gives private servers outbound internet access without accepting inbound connections, and it requires reserved IP addresses. The standard three-tier NAT Gateway pattern places load balancers and web servers in a public subnet, routes the private application subnet's outbound traffic through a NAT Gateway, and keeps database servers in a dedicated private subnet with no direct internet path. That is the layered shape with its egress path drawn in.

2.3 FinCorp's First Layout

FinCorp's customer portal follows the canonical shape in one German VDC:

 Internet
    |
 [Public LAN]  Managed Application Load Balancer (public listener, TLS offloading)
    |
 [App LAN]     Stateless portal servers / Managed Kubernetes node pools
    |                      \--> Managed NAT Gateway --> AI Model Hub, external APIs
 [Data LAN]    Managed Network Load Balancer (private listener)
    |
               DBaaS for PostgreSQL, DBaaS for In-Memory DB, Event Streams for Apache Kafka
               (no internet access element on this LAN)

 Connected sites: Private Cloud (regulated VMware workloads), on-premises via VPN Gateway

The design keeps the regulated core-banking workloads in Private Cloud as a connected site, so FinCorp retains its VMware operating model while the portal tier runs on elastic VDC compute. Later modules decide each box: the addressing and NIC filtering (Module 3), the compute classes (Module 4), the database replication mode and cache (Module 5), and the cluster design (Module 6).

Decision Summary

Layer Default product Exposure Choose differently when
Edge Managed Application Load Balancer, public listener Internet, reserved public IP Traffic is not HTTP or HTTPS, or TLS must reach the backend untouched: use a Layer 4 path
Compute Compute Engine, Cubes, VM Auto Scaling replicas, Kubernetes node pools Private LAN Never public; outbound access goes through the Managed NAT Gateway
Internal balancing Managed Network Load Balancer, private listener Private LAN You need HTTP-aware east-west routing: use a private ALB listener
Data DBaaS engines, Event Streams for Apache Kafka Private LAN with no internet access element External administrative access is a separate, deliberate design (Unit 5.3)
Attached Private Cloud, on-premises, AI Model Hub, Object Storage Connected site or endpoint Never fold them into a public LAN to simplify routing

Summary

The canonical layered architecture follows from three platform facts. Exposure is a property of the LAN, the ALB and NLB serve different traffic types and can be public or private, and NIC-level filters protect servers rather than managed services. Put the public Layer 7 edge in front, keep compute stateless and private, balance internally at Layer 4, and leave the data tier with no internet path. Other families attach as node pools, connected sites or endpoints, and the Managed NAT Gateway supplies outbound access without opening an inbound one.

Key Points:

  • Attaching the internet element converts a private LAN to a public one, including its IP addresses; design exposure LAN by LAN.
  • Use the ALB where routing needs HTTP attributes; use the NLB where TCP routing performance matters.
  • Neither the ALB nor the NLB supports SNAT, so private tiers need the Managed NAT Gateway for outbound access.
  • Network Security Groups and the NIC-based Firewall protect server NICs; topology isolates the data tier.
  • Kubernetes, Private Cloud, AI Model Hub and hybrid links attach to the shape; they do not add a tier.