If I'm reading this right, Amazon Route 53 supports up to 5 API requests per second writing up to 10^3 records per request. Also, writes are free, while reads cost as little as $0.20 / 10^6 -- cheaper than DynamoDB! I'm... seriously considering using Route 53 as a database.
-
Show this thread
-
I mean, seriously: DynamoDB has (at great expense!) Global Tables... but Route 53 is not only replicated between AWS Regions, it's replicated to every single AWS edge point *at no added expense*.
3 replies 4 retweets 42 likesShow this thread -
If you want to access a database from a Lambda@Edge function, I can't imagine how any alternative offered by Amazon would come close to using Route 53, on either pricing or performance.
2 replies 4 retweets 27 likesShow this thread -
I really hope that someone from Amazon (
@colmmacc maybe?) tells me why this is a bad idea soon, because otherwise I'm going to start writing some code.11 replies 4 retweets 82 likesShow this thread -
Replying to @cperciva
Well here's a few things! One of the defining abilities of a database is the ability to make structured queries. Route 53 can do simple key -> value, but how do you an ordered search in DNS? or conditions?
2 replies 2 retweets 8 likes -
Next, although we provide an API that tells you when changes go in-sync, so you can treat Route 53 itself as strongly consistent, DNS comes with caches and they are eventually consistent. Building on top of that could be challenging!
1 reply 0 retweets 6 likes -
Related is that the reads also all come with no authz/authn. Everything is public, and there's no logs for those cache hit reads!
5 replies 0 retweets 6 likes -
(you could use private zones, right?)
1 reply 0 retweets 1 like
True! Private zones will only be queryable in the VPCs you associate them with. Btw, you now also have table spaces!
-
-
what is the intersection of folks who have outgrown the free tier but are so cost-sensitive that using DNS as a datastore is worth the
* development time
* tail risk of surprising behavior/explosion0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.