Skip to content

Instantly share code, notes, and snippets.

@cisene
Last active March 17, 2023 08:02
Show Gist options
  • Save cisene/5b6bf366ae4d8b62c03571e6ee89ba98 to your computer and use it in GitHub Desktop.
Save cisene/5b6bf366ae4d8b62c03571e6ee89ba98 to your computer and use it in GitHub Desktop.
GUID-URN resolution
Looking at the DNS/FQDN based GUID resolver.
* Heavy on DNS resulution - latencies
https://396d9ae0da7e5557b894b606231fa3ea.guid.podcastindex.org/ resolves to https://feeds.buzzsprout.com/1538779.rss
If flipped around, the following pattern might be used;
https://guid.podcastindex.org/396d9ae0da7e5557b894b606231fa3ea
* could produce same result but would not require new DNS resolution
* does not "pollute" the DNS space
* allows for "prefetch" (pre-resolution in browsers)
A counter part URN service would be set up to provide resolution the other way, which could overlap (Many-to-one)
https://urn.podcastindex.org/urn/com/buzzsprout/feeds/1538779 or
https://urn.podcastindex.org/urn:com:buzzsprout:feeds:1538779
Which could overlap with an equivalent, a copied feed on another hosting servce but that resolves to the same GUID ..
https://urn.podcastindex.org/urn:fm:anchor:feeds:c0ffee123
Caching
Redis - all-in-one, easy to update cache, persisted-to-disk in-memory.
Varnish - cache to disk as disk storage is cheap and memory is expensive.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment