Engineering innovation. Empowering businesses.[email protected]
Home / Request Journey

Interactive architecture presentation

See the complete journey
behind one request.

Choose a website visit, mobile action, or API call. Then follow it through DNS, secure connectivity, the application, its data, and the response back to the user.

Inside every request

One click.
A whole journey.

Follow a website visit, mobile app action, or API call from DNS lookup to the server and back. Choose where the application runs, then watch each exchange.

WEB BROWSERhttps://dhruvexa.com/SIMULATION
Request & response explorerIllustrative • no live traffic
From the user to DNS, application hosting, and back A device asks a recursive resolver for an address. The resolver consults root, top-level domain, and authoritative DNS servers. The device connects to a public edge, which routes the request to a cloud or private application. The application queries its database and returns a response through the edge to the device. DNS does not carry the website request. 01 / FIND THE ADDRESS 02 / CONNECT, REQUEST, RESPOND PUBLIC CLOUD · AZURE / AWS / GOOGLE CLOUD PRIVATE DATA CENTER PRIVATE LINK / VPN YOUR DEVICE Browser / mobile / API client DNS RESOLVER Recursive lookup + cache ROOT DNS Where is .com? .COM DNS Who serves dhruvexa.com? AUTHORITATIVE DNS Address record + TTL PUBLIC EDGE TLS / WAF / reverse proxy CLOUD APPLICATION Web server / API service CLOUD DATABASE Private application data PRIVATE APPLICATION Web server / API service PRIVATE DATABASE Private application data DNS finds the address. HTTPS carries the request and response. Only the application talks to its database.

← Swipe to explore the full journey →

DNS lookup / replyConnection / requestResponse / return
READY / WEBSITE VISIT

What happens after you click?

A fresh DNS lookup finds the public endpoint. A secure connection carries the request to an application, which returns a response to your device.

Choose a scenario, then start or step through the journey.

Journey so far 0 steps

  1. Waiting for your first request.

Select an infrastructure component to inspect its role.

Illustrative sequence, slowed down for learning—not live monitoring or measured latency. This example uses a fresh HTTPS connection, an edge cache miss, and a database-backed page or API. Real systems may reuse connections, serve cached content, follow CNAMEs, or use different network routes. Browser CSS, scripts, and images can trigger additional requests.

Explore infrastructure services ↗
Go one layer deeperExplore Advanced Network LabDiscover how IP addresses, NAT, packet routing, firewalls, and secure infrastructure really work.

Three architectures. Three clear boundaries.

Where does your
application live?

Explore a separate high-level diagram for each cloud model. These are illustrative designs, not a map of Dhruvexa production infrastructure. Select a component to learn what it does.

01

Public cloud

Provider-managed infrastructure. Private application data.

HIGH-LEVEL MODEL
Public cloud architecture User to Public CDN / WAF to Cloud ingress to Application / API to Private database. Responses return through the same logical components. A public-cloud provider operates the resource pool. Public cloud does not mean every service has a public IP: application targets and databases can stay private. PUBLIC CLOUD · PRIVATE APPLICATION / DATA SUBNETS User Select to inspect Public CDN / WAF Select to inspect Cloud ingress Select to inspect Application / API Select to inspect Private database Not exposed to users CYAN → REQUEST / SERVICE CALLGREEN ← LOGICAL RESPONSE PATH

A public-cloud provider operates the resource pool. Public cloud does not mean every service has a public IP: application targets and databases can stay private.

Elastic capacity · managed services · usage-based operation

Select a component above for its technical role and business value.
02

Private cloud

A dedicated cloud environment for one organization.

HIGH-LEVEL MODEL
Private cloud architecture Authorized user to Site firewall to Private ingress to Private compute to Private database. Responses return through the same logical components. A private-cloud control plane provisions a dedicated pool of compute, network and storage resources. This is more than placing a single server behind a private IP. Access can be internal or through explicitly protected ingress. PRIVATE CLOUD · DEDICATED RESOURCE POOL + CONTROL PLANE Authorized user Select to inspect Site firewall Select to inspect Private ingress Select to inspect Private compute Select to inspect Private database Not exposed to users CYAN → REQUEST / SERVICE CALLGREEN ← LOGICAL RESPONSE PATH

A private-cloud control plane provisions a dedicated pool of compute, network and storage resources. This is more than placing a single server behind a private IP. Access can be internal or through explicitly protected ingress.

Controlled capacity · dedicated resources · organization-operated policies

Select a component above for its technical role and business value.
03

Hybrid cloud

Public-cloud applications. Connected private-cloud services.

HIGH-LEVEL MODEL
Hybrid cloud architecture User to Public edge to Cloud application to VPN / private link to Private-cloud data. Responses return through the same logical components. Distinct public and private cloud environments are joined by configured connectivity. In this example the app runs in public cloud and queries a private-cloud database. Routing, latency, identity and firewall policies must work across both environments. PUBLIC CLOUD PRIVATE CLOUD User Select to inspect Public edge Select to inspect Cloud application Select to inspect VPN / private link Controlled connectivity Private-cloud data Not exposed to users CYAN → REQUEST / SERVICE CALLGREEN ← LOGICAL RESPONSE PATH

Distinct public and private cloud environments are joined by configured connectivity. In this example the app runs in public cloud and queries a private-cloud database. Routing, latency, identity and firewall policies must work across both environments.

Workload placement · controlled data location · connected operations

Select a component above for its technical role and business value.