[Last Week in AWS Extras]: Route 53, Amazon’s Premier Database

 

The problem with having a few running jokes in this newsletter is that if you weren't around when I came up with them (or, heaven forbid, you skipped an issue), they may not make much sense. Today we explore my Route 53 as a Database schtick.

 

As always, should you wish to link someone else to this post, you can forward it, or else view it on the web.

 

 

Sponsorships are fun sometimes.

 

ParkMyCloud: "Can we have one of our execs do a video chat with you?"

 

Me: "Better idea, how about I talk to one of your customers instead so we can make fun of you on your dime?"

 

It turns out I'm SUUUPER convincing, so that's what's happening! Join me and ParkMyCloud's customer Workfront TOMORROW for a no-holds-barred discussion about how they're optimizing AWS costs, and whatever other fights I can pick before ParkMyCloud realizes what's going on and kills the feed!

 

Register here to catch the fun. Sponsored

 

 

Route 53, Amazon's Premier Database

I've periodically made reference in a bunch of places to Route 53 being my preferred database.

 

But I've only really told the story in podcast and tweet thread form. I've never gone in depth as to how this terrible, terrible antipattern came to be in a blog post—which is far easier to cite.

 

Today is your lucky day!

 

Before I begin, I want to emphasize that this is tongue-in-cheek. Please do not do this.

 

There are, in 2020, far better ways to solve this problem.

DNS isn't really a database

Many years ago, I worked at a company that looked a lot like a traditional on-premises build-out, because it was. Cloud was nascent in those days, and the 2008 financial collapse was yet to come. We had a bunch of virtual machines (VMs) that were themselves running on physical hosts in racks.

 

Everything you might expect of such an environment was true. We had cabling problems, we bled on the rack nuts, we drove at unsafe speeds in the middle of the night to frantically restore service when things broke.

 

As I said, it was a different time.

 

We had some limited ability to migrate VMs between physical hosts. Live migration didn't work in our configuration, so these VMs tended to stay pretty much where we put them. This led to a series of problems that in hindsight were entirely avoidable.

 

Note to future self: You have two DNS resolvers for redundancy; perhaps do not put them both on the same physical host.

 

Which of course brings us to DNS.

 

We wanted to know in a hurry upon which host any given VM lived, so we struck upon a somewhat novel solution. DNS TXT records are a type of resource record in DNS that support arbitrary strings. They're used for a variety of "validate you own the domain," DMARC / SPF spam reduction systems, DNS-based service discovery, and other various use cases. Being the geniuses we were, we struck upon the idea of using these records to set each VM's host VM.

 

From there, it didn't take us too long to hit upon the idea that this worked super well with our sysadmin scripting language of choice: crappy shell scripts. dig TXT vm1.web.prod.ord.twitterforpets.com returned a neat defiant.prod.ord.twitterforpets.com answer. (We'll save my "Federation Starships" server naming convention for another day.) Thus, it became super easy for us to work this into our crappy management scripts.

 

"Validate that the physical host has no more VMs on it BEFORE you yank the power cable out" stopped being a sticky note that got ignored. Instead, it became a script that was generally ignored instead until right after it really needed to have worked. "This VM seems slow, which host is it on?" was now a quick DNS query away. And times were good.

 

Of course, this is horrifying today.

 

Most environments have a control plane that can give you these answers in the form of metadata. It's also close-to-but-not-the-most horrifying abuse of tagging possible in a cloud environment.

 

Functionally, what you're really looking for is something like a configuration management database or something fairly robust like Device 42. Instead of twisting low-level primitives (not to mention yourself) in knots, use something that's purpose-built for the task at hand.

And yet...

Route 53 (Amazon's managed DNS service) is the only AWS service with a public 100% SLA on the data plane. It incurs no charges for data transfer anywhere inside of AWS or out to the internet. As long as you move a hosted zone to either a new zone or a different AWS account within 12 hours, the 50¢ per month charge per zone doesn't apply.

 

The world has been rife with misuses of DNS: serving as a tunnel, a filesystem, and a DDoS cannon, for example. As such, viewing it as a database isn't the strangest idea in the world.

 

And so...

Route 53 is a database

I do declare that Route 53 is in fact a database.

 

There are libraries to make it more user-friendly to query. Every system, every language, and every SDK knows how to speak to it. It loses considerably less data than MongoDB. The pricing is reasonable even without weasel-tricks to get around it. And its underlying technology has been proven out over decades.

 

It provides "CA" on the CAP theorem conjoined triangle of success. It is, for the moment, non-relational. And it's super hard to raise $2 billion in venture money from Softbank around a technology this unexciting.

 

All of that goes to show that DNS—and, by extension, Route 53—is not only a perfectly suitable database option, it’s the best database money can buy.

 

I dare you to prove me wrong.

 

 

When using Amazon’s Elastic Kubernetes Service (EKS), you must understand which pieces of the security management role fall on you. Use this 42-page eBook from StackRox to learn about EKS cluster security, including the standard controls and best practices for minimizing the risk around cluster workloads, as well as specific requirements for securing an EKS cluster and its associated infrastructure. Sponsored

 
 
 
Corey

I’m Corey Quinn

I help companies address their horrifying AWS bills by both reducing the dollars spent and helping them understanding what they’re paying for.

 
 
The Cloud

Screaming in the Cloud & AWS Morning Brief

In addition to this newsletter, I host two podcasts: Screaming in the Cloud, about the business of cloud computing, featuring me talking to folks who are good at things; and AWS Morning Brief, a show about exclusively AWS with my snark at full-tilt.

 
 
The Cloud

Sponsor an Issue

Reach over 19,000 discerning engineers, managers, and enthusiasts who actually care about the state of Amazon's cloud ecosystems.

 



Want to skip these Last Week in AWS Extras? Click here and you won't receive these Wednesday dispatches anymore.

To make sure you keep getting these emails, please add corey@lastweekinaws.com to your address book or otherwise mark me as a permitted sender.

Want out of the loop completely? Click here to tell me to leave you alone.

 

Duckbill Group

1728 Ocean Ave #307, San Francisco, CA 94112

 
                                                           

Older messages

[Last Week in AWS] Issue #171: AI/ML Marketing Algorithm Continues to Malfunction

Monday, July 20, 2020

Good morning! For those relatively new to the list, it's time once again for my periodic "here's what I do for a living" story. At the Duckbill Group we fix the horrifying AWS bills,

[Last Week in AWS Extras]: The Lock-In You Don’t See

Thursday, July 16, 2020

Today's email departs from the past few weeks' "hilarious" vein and drifts back towards a general analysis tone. Today's topic: lock-in! As always, should you wish to link someone

[Last Week in AWS] Issue #170: AWS Machine Learning Your Business From Inside

Monday, July 13, 2020

Good Morning! Last week saw a bunch of things, from my ridiculous Jeff Barr birthday video to my suggestion for a new AWS service to a bunch of sad things in the news. I'll be keynoting Cloud

[Last Week in AWS Extras]: Introducing AWS Elastic Beanstalker

Wednesday, July 8, 2020

Today's email is half whimsy, half a viable-if-outlandish solution to solve the AWS billing system's problems in one go. Honestly, at this point I can't tell if it's a completely

[Last Week in AWS] Happy 60th Birthday Jeff Barr!

Tuesday, July 7, 2020

Happy birthday to one of our favorite people, AWS Chief Evangelist and VP Jeff Barr. As is our tradition here at the Duckbill Group, we've created a music video to celebrate the equation. Without

You Might Also Like

SWLW #592: Advice that I can't get out of my head, The Compass vs. Map method, and more

Friday, March 29, 2024

Weekly articles & videos about people, culture and leadership: everything you need to design the org that makes the product. A weekly newsletter by Oren Ellenbogen with the best content I found

ASP.NET Core News - 03/29/2024

Friday, March 29, 2024

View this email in your browser Get ready for this weeks best blog posts about ASP.NET Core! This newsletter is sponsored by elmah.io - the most advanced, yet so simple to set up, error logging and

New Linux Bug Could Lead to User Password Leaks and Clipboard Hijacking

Friday, March 29, 2024

THN Daily Updates Newsletter cover Refactoring in Java ($36.99 Value) FREE for a Limited Time Refactoring in Java serves as an indispensable guide to enhancing your codebase's quality and

Post from Syncfusion Blogs on 03/29/2024

Friday, March 29, 2024

New blogs from Syncfusion Introducing the New .NET MAUI Chat Control By Piruthiviraj Malaimelraj This blog explains the features of the new Syncfusion .NET MAUI Chat control added in the 2024 Volume 1

Re: Last Chance

Friday, March 29, 2024

Dear there, By this time tomorrow, your exclusive new subscriber discount will be gone and you'll have to pay twice as much to join Insider and master everything your iPhone has to offer. If, like

Hacker Newsletter #694

Friday, March 29, 2024

Always forgive your enemies - nothing annoys them so much. //Oscar Wilde hackernewsletter Issue #694 // 2024-03-29 // View in your browser Happy Easter if you celebrate it! Heads up - we're taking

Apple RCS 📱, SBF's 25 year sentence 👮, Linux Foundation's Redis fork 👨‍💻

Friday, March 29, 2024

RCS is coming to the iPhone in the fall of 2024 Sign Up|Advertise|View Online TLDR Together With Veracode TLDR 2024-03-29 Build fast, build secure (Sponsor) Software is drowning in security debt.

Data Science Weekly - Issue 540

Friday, March 29, 2024

Curated news, articles and jobs related to Data Science, AI, & Machine Learning ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏

This Week in Rust #540

Friday, March 29, 2024

Email isn't displaying correctly? Read this e-mail on the Web This Week in Rust issue 540 — 27 MAR 2024 Hello and welcome to another issue of This Week in Rust! Rust is a programming language

The Value Of A Promise 🤞

Friday, March 29, 2024

How much is a promise from a tech company really worth, anyway? Here's a version for your browser. Hunting for the end of the long tail • March 28, 2024 The Value Of A Promise When you hear a