IPNS in a production environment

So I wanted to ask about re providing IPNS records to the network and doing this in a production environment… The simplest and easiest way to do this would be to simply do a resolve on a ipns name, cache the content, then circle back to it later to check for updates. I already do this in my project called Fierro. This means if no updates through the DHT are found, then keep caching the same old content. What are other ways to support this mission? I understand there is an Accelerated DHT option in Kubo and IPNS over Pubsub could help but what are the tradeoffs in a production environment?

1 Like