Unified Edge Router
The Exovon Unified Edge Router acts as the intelligent front-door for all traffic entering your infrastructure. Built on a globally distributed Anycast mesh with primary edge hubs across India (Mumbai, Delhi, Bengaluru, Chennai), it automatically bifurcates static assets, serverless execution, and container traffic with sub-30ms latency.
Intelligent Path Splitting
Routes static files directly to Tier-1 Edge CDN caches while proxying dynamic API requests to warm serverless compute units.
Zero-Downtime Rollbacks
Atomic edge routing pointer updates allow instant traffic redirection to previous revisions in < 3 seconds without DNS lag.
Automated SSL & WAF
Auto-renewing TLS 1.3 certificates, HTTP/3 QUIC termination, rate-limiting, and DDoS protection at the network edge.
1. The Request Routing Pipeline
When an HTTP/HTTPS request hits your custom domain or *.exovon.co.in URL, the Edge Router performs high-speed L7 inspection and dispatches it through specialized pipelines:
| Path Pattern | Destination | Default Cache Strategy | Target Latency |
|---|---|---|---|
| /_next/static/*, /assets/* | Edge CDN Storage Buckets | public, max-age=31536000, immutable | < 25ms |
| /favicon.ico, /robots.txt | Edge CDN Cache | public, max-age=86400 | < 30ms |
| /api/*, /graphql | Serverless Compute (gVisor) | no-cache, private, no-store | ~60ms (Warm) |
| /* (SSR HTML Pages) | Dynamic SSR Serverless Unit | s-maxage=60, stale-while-revalidate | ~80ms |
2. Progressive Canary Shifting
To protect production traffic from catastrophic deployment regressions, Exovon uses automated canary traffic gates:
Pre-Flight Health Probe (0% Traffic)
The Edge Router sends synthetic HTTP probes to the newly compiled container. It must return 200 OK and pass TCP handshake checks within 10 seconds.
Canary Traffic Bleed (10% Traffic)
10% of live incoming user sessions are routed to the new build for a 60-second observation window. Active 5xx error rates and latency percentiles (p95/p99) are monitored.
Full Promotion (100% Traffic)
If the error rate remains under 0.1%, the router atomically promotes the new revision to 100%. If an anomaly is detected, traffic immediately falls back to the previous deployment.
3. Custom Headers & Edge Rules
Configure security headers, CORS origins, and caching rules directly inside your next.config.mjs or root exovon.config.json:
Frequently Asked Questions
How does Exovon prevent 502 Bad Gateway errors during rollbacks?
The Edge Router maintains connections via keep-alive and updates routing tables atomically in memory. New requests are pointed to the target deployment instantly, while in-flight requests finish processing on the old container.
Are custom domains protected against DDoS attacks?
Yes. All custom domains proxied through Exovon benefit from automated Layer 3/4 SYN flood protection and Layer 7 volumetric HTTP flood filtering at edge points of presence across India.