TechOps Examples
Hey — It's Govardhana MK 👋
Welcome to another technical edition.
Every Tuesday – You’ll receive a free edition with a byte-size use case, remote job opportunities, top news, tools, and articles.
Every Thursday and Saturday – You’ll receive a special edition with a deep dive use case, remote job opportunities and articles.
Top engineers at Anthropic and OpenAI say AI now writes 100% of their code.
If you're not using AI, you're spending 40 hours doing what they do in 4.
These 100+ Claude Code hacks fix that and help you ship 10x faster.
Sign up for The Code and get:
100+ Claude Code hacks used by top engineers — free
The Code newsletter — learn the latest AI tools, tips, and skills to code faster with AI in 5 minutes a day
🛠 TOOL OF THE DAY
amazon ecr credential helper - Automatically gets credentials for Amazon ECR on docker push/docker pull.
🧠 USE CASE
Cloud DNS Routing Policies BreakDown
Have you ever wondered why an OTT subscription registered in India won’t work in the USA or why a soccer game live in Europe isn’t available in Singapore?
The answer often lies in sophisticated DNS routing policies designed to deliver content efficiently, securely, and sometimes legally.
Let’s explore six key DNS routing policies that power global-scale applications and their real-world applications, benefits, and limitations.
1. Simple Routing
DNS maps a domain (e.g., app.techops.com) to a resource like an EC2 instance, load balancer, or Kubernetes service, resolving to a single IP.
It uses A/AAAA records for static IPs or CNAME records for dynamic resources like ALBs.
If the resource fails, traffic halts unless manually rerouted.
2. Weighted Routing
Multiple resources are assigned weights, and DNS resolves requests proportionally to these weights. Example: 70% to v1.techops.com, 30% to v2.techops.com
Each DNS entry gets a percentage weight.
If all resources have weight=0, traffic is evenly distributed
3. Failover Routing
Configures a primary and secondary resource for disaster recovery (DR). Traffic routes to the primary unless health checks detect a failure, in which case it redirects to the secondary.
Monitors HTTP(S), TCP, or even custom endpoint responses for health checks.
DNS TTL impacts failover speed; typical values range from 30–60 seconds.
4. Latency Based Routing
Routes users to the resource with the lowest network latency. Latency is dynamically calculated using regional edge locations and network topology.
DNS resolver queries latency maps updated by the DNS provider (e.g., Route 53 or Akamai).
Relies on GeoIP databases and BGP routing data.
5. Geolocation Routing
Routes users based on their IP location to pre-defined backend regions.
Uses GeoIP databases to map user IPs to locations.
Pre-configured locations specify which region serves traffic.
Supports default routing for unmatched locations.
6. Geoproximity Routing
Routes users to the nearest resource while adjusting traffic distribution with a bias factor.
Bias ranges from
-99to99:Positive bias sends more traffic to a resource.
Negative bias sends less traffic to a resource.
Geo-proximity calculations use lat/lon coordinates of resources and user IPs.
Pro Tip: When implementing these policies, always monitor real-world traffic patterns and tweak TTL, weights, and biases dynamically for optimal results.
Looking to promote your company, product, service, or event to 50,000+ TechOps Professionals? Let's work together.
