Nuxt 3 on Vercel - Store cache in memory vs Vercel KV ?
Hi everyone, I developed this habit of always tying every new Nuxt project to a Vercel KV store. But every now an then, I'm facing this issue where the store reaches 5-7k keys (300b to 12kb each) , even though I only have 50 pages on some of the websites, and I can't seem to delete a single key or even flush the entire store using
I use this setup to store my API responses so I don't have to fetch the same content over and over.
I set up a process in order to clear some cache entries on content updates on the CMS and also on Vercel deployments. But sometimes it's hard to know every single part of the website you need to clear the cache for, so I get some pages that don't reflect the latest changes.
Where am I going with all this....I'm suddenly asking myself if this whole KV thing is actually giving me some advantages compared to a simple memory storage, knowing that I don't need this data to be persisted between deployments. Using the memory driver, I could still invalidate some pages cache the same way I do it at the moment, and the entire cache would be flushed on a new Vercel deployment.
It would work perfectly for me, I don't think I really need a KV store, but I wonder if I would feel some big difference in terms of performance. I'm also looking at the LRU cache driver.
I'd greatly appreciate your input on this.
useStorage().removeItem()useStorage().clear()I use this setup to store my API responses so I don't have to fetch the same content over and over.
I set up a process in order to clear some cache entries on content updates on the CMS and also on Vercel deployments. But sometimes it's hard to know every single part of the website you need to clear the cache for, so I get some pages that don't reflect the latest changes.
Where am I going with all this....I'm suddenly asking myself if this whole KV thing is actually giving me some advantages compared to a simple memory storage, knowing that I don't need this data to be persisted between deployments. Using the memory driver, I could still invalidate some pages cache the same way I do it at the moment, and the entire cache would be flushed on a new Vercel deployment.
It would work perfectly for me, I don't think I really need a KV store, but I wonder if I would feel some big difference in terms of performance. I'm also looking at the LRU cache driver.
I'd greatly appreciate your input on this.
