Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • Good job, Colin.

    I see you are following the Dyna53 [1] steps ;) What a school of thought you have sparked, Corey!

    [1]: https://dyna53.io/

  • > If the same record is changed in the file system and in Route 53 at the same time, we aim for last-write-wins. This is not strictly possible, since Route 53 does not expose modification timestamps on records

    Except route 53 provides a fully ACID transactional API you can build your own locks with!

  • Route53 makes a great, simple, HA key-value store for some use cases. I've used it in GitHub Actions when nothing else was easily available to store values and put a little post together explaining how a while back. For many things, there isn't a reason for more complexity.

    https://doug.sh/posts/route53-as-a-key-value-store-2026-edit...

  • At first I thought this was a general purpose file system over R53, ala Corey Quinn. But my, what a gorgeously terrible idea. Well done.
  • A “schema that reads like XML that learned JSON in prison” IM DEAD

    Stealing this. Gold lies at the intersection of cperciva and quinnypig.

  • Speaking as a former Blog Bar Raiser, cperciva has internalized the AWS blog style guide better than most Amazonians. This is spot-on.
  •     > Q. Is this HIPAA compliant?
        > A. Please do not store patient information in DNS.
    
    love this. reminds me a little of something else in the realm of DNS "hosting" posted to hn a few years ago [0][1]

    [0]https://banner.triweb.dev [1]https://news.ycombinator.com/item?id=39502097

Explore Birbla archives