<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure on Sohil Ladhani Blog</title><link>https://sohilladhani.com/blog/tags/infrastructure/</link><description>Recent content in Infrastructure on Sohil Ladhani Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 25 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sohilladhani.com/blog/tags/infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>Anycast and PoP Placement</title><link>https://sohilladhani.com/blog/post/2026-07-25-anycast-and-pop-placement/</link><pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate><guid>https://sohilladhani.com/blog/post/2026-07-25-anycast-and-pop-placement/</guid><description>Cloudflare has 300+ Points of Presence (PoPs) globally. When you make a request to a Cloudflare-protected site, you don&amp;rsquo;t connect to a server in a specific city — you connect to the nearest Cloudflare PoP, wherever that is. This works via anycast: multiple servers worldwide share the same IP address, and BGP routing delivers your packets to the geographically closest one. PoP placement and anycast are the foundation of how CDNs achieve global low latency.</description></item><item><title>DNS-Based Traffic Routing</title><link>https://sohilladhani.com/blog/post/2026-07-23-dns-based-traffic-routing/</link><pubDate>Thu, 23 Jul 2026 00:00:00 +0000</pubDate><guid>https://sohilladhani.com/blog/post/2026-07-23-dns-based-traffic-routing/</guid><description>DNS returns an IP address. It doesn&amp;rsquo;t have to return the same IP address every time. The authoritative nameserver can return different IPs based on where the query originated, which backend is healthy, or how much traffic each backend should receive. DNS-based traffic routing uses this flexibility to implement geographic routing, load balancing, and failover without changing a line of application code.
GeoDNS The recursive resolver&amp;rsquo;s IP address reveals the approximate location of the client (or at least the ISP).</description></item><item><title>DNS Resolution</title><link>https://sohilladhani.com/blog/post/2026-07-22-dns-resolution/</link><pubDate>Wed, 22 Jul 2026 00:00:00 +0000</pubDate><guid>https://sohilladhani.com/blog/post/2026-07-22-dns-resolution/</guid><description>Every system design interview starts with a client making a request. Before that request reaches your load balancer, DNS has already run. DNS translates api.example.com into an IP address. It&amp;rsquo;s a globally distributed read-heavy system that handles 3.5 trillion queries per day. Understanding how resolution works explains why DNS changes take time to propagate and how DNS-based traffic routing is possible.
The Resolution Chain A DNS query for api.example.com follows a chain of four server types:</description></item></channel></rss>