Unified Edge Router
The Exovon Edge Router acts as the intelligent ingress tier for incoming traffic. Operating on an Anycast mesh with primary edge hubs across India (Mumbai, Delhi, Bengaluru, Chennai), it routes static assets, serverless runtimes, and containers with sub-30ms domestic latency.
Intelligent Path Splitting
Routes static assets directly to edge CDN points of presence while proxying dynamic serverless and API requests to warm compute containers.
Atomic Traffic Shifts
In-memory routing pointer updates switch traffic between deployments or roll back to prior releases in <3 seconds without DNS propagation delay.
Automated SSL & WAF
Auto-renewing TLS 1.3 certificates, HTTP/3 QUIC termination, rate-limiting, and volumetric DDoS mitigation at the edge.
Request Routing Strategy
When a request reaches your domain or assigned *.exovon.co.in URL, the edge router evaluates path rules and dispatches to the optimal destination:
| Path Pattern | Destination Target | Cache Header Policy | Target Latency |
|---|---|---|---|
| /_next/static/*, /assets/* | Edge CDN Storage | public, max-age=31536000, immutable | < 25ms |
| /favicon.ico, /robots.txt | Edge CDN Cache | public, max-age=86400 | < 30ms |
| /api/*, /graphql | Serverless Container (Mumbai) | no-cache, private, no-store | ~60ms (Warm) |
| /* (SSR HTML Pages) | Dynamic SSR Container | s-maxage=60, stale-while-revalidate | ~80ms |
Progressive Canary Rollouts
To prevent deployment regressions from degrading user sessions, Exovon enforces phased traffic gates:
Pre-Flight Health Probing (0% Traffic)
The router dispatches synthetic TCP and HTTP probes to the freshly compiled container on port 8080. The runtime must return 200 OK within 10 seconds before proceeding.
Canary Verification (10% Traffic)
10% of live incoming user sessions route to the new revision during a 60-second observation window while 5xx error rates and p99 latency metrics are continuously monitored.
Production Promotion (100% Traffic)
If the error threshold remains under 0.1%, the router atomically promotes the new revision to 100%. If an anomaly occurs, traffic immediately rolls back to the prior deployment.
Security Headers & Edge Rules
Configure custom response headers, CORS policies, and security headers directly inside your application configuration:
// Security and framing header configuration
export default {
output: "standalone",
async headers() {
return [
{
source: "/:path*",
headers: [
{ key: "X-Frame-Options", value: "DENY" },
{ key: "X-Content-Type-Options", value: "nosniff" },
{ key: "Referrer-Policy", value: "strict-origin-when-cross-origin" },
{ key: "Strict-Transport-Security", value: "max-age=63072000; includeSubDomains; preload" },
],
},
];
},
};Frequently Asked Questions
How does Exovon prevent 502 errors during rollbacks?
The Edge Router maintains connections via keep-alive and updates routing tables atomically in memory. New requests route to the target deployment instantly, while in-flight requests finish processing on existing containers.
Are custom domains protected against DDoS attacks?
Yes. All custom domains proxied through Exovon benefit from Layer 3/4 SYN flood protection and Layer 7 volumetric HTTP filtering across Anycast edge nodes in India.