First Steps: Domain Resolution & Ingress Flow

Level 1social

Architect secure web traffic ingress: resolve domain names through DNS / CDN and route requests into an API Server.

Building Blocks

Drag onto canvas or click + to add.

Client (Web / App)

Mobile & browser apps

DNS / CDN

Edge routing & static caching

API Gateway / Server

Auth & request routing

Backend Service

Business domain service

Scenario Background

You are setting up the foundation for a new web service. In production, browsers never connect to hardcoded origin server IPs. You need to establish a resilient ingress flow: routing browser traffic through DNS / CDN for edge caching and DDoS protection before terminating requests at an API Gateway / Server.

Capacity & Traffic Targets

Incoming Traffic	100 requests/minute
Protocol	HTTP/2 over TLS
Average Response Time	< 25 ms

Functional Requirements

1Resolve public domain name queries to CDN edge IPs
2Terminate HTTP GET and POST requests from web and mobile browsers
3Route dynamic requests to the API Gateway with status 200 OK responses

Non-Functional Requirements

Latency: Under 50ms for basic request-response termination
Edge Protection: Origin server IP must not be directly exposed to clients

Core Constraints

• No direct connection from Client to API Server (must traverse DNS / CDN)