What is the Alchemy Edge Proxy?
Article excerpt
What is the Alchemy Edge Proxy? Think of the Edge Proxy as the front door to Alchemy's RPC infrastructure. Every API request, whether it is reading Ethereum state, querying Solana accounts, or submitting a transaction on Base, passes through this ingress layer before reaching the serving infrastructure behind it. For years at Alchemy Alchemy used a major CDN as that front door. CDNs are a popular industry choice for good reason: they ship out of the box with DDoS protection, geographic routing, WAF rules, and SSL termination. For most web applications, that bundle is good enough. CDNs have spent two decades being the default ingress layer for everything from e-commerce to streaming, and they earn that position. Onchain finance has different demands. RPC traffic is bursty, latency-sensitive, geographically global, and security-critical in ways that ordinary web traffic is not. A trading bot reading state across three chains in parallel does not care that a CDN can cache a marketing page in 50 cities. It cares about the time between issuing eth_call and getting a response. A wallet syncing balances does not need a WAF rule for SQL injection. It needs the closest possible edge node and a TLS handshake that completes in single-digit milliseconds. A protocol settling positions on a derivatives exchange cannot tolerate a third-party CDN's incident timeline as a ceiling on its...
Keep reading with a free account
The rest of this article, and every signal for Alchemy, is in your free account.
Extracted from this sentence
To meet those demands, Alchemy built a custom edge proxy on bare metal: a purpose-built ingress layer designed from the ground up for high-throughput, low-latency blockchain RPC traffic.
