{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"All Play w/ Ryan Hefner","title":"036 — Pedal to the Metal","html":"","width":"100%","height":180,"duration":804,"description":"Watch the video on YouTube: https://youtu.be/rLRNnlzIOQM\nI connected with Vercel this past week to discuss how I could both optimize and try to control the costs that https://www.starterpacks.net was accumulating. I did walk away with some techniques that I will try on the next site I launch on Vercel where I need to try to maintain a consistent bill. Most notably:\nFluid Compute is good and does reduce function use/chaos\nControlling the cache key to maintain the cache between deploys (when possible)\nPlay with Cache-Control headers to see if it's possible to increase the number of cached edge request hits, and ultimately skip the function rendering for each cached page\n\nSo, some good pointers to keep in mind for the next site that takes off on Vercel.\nOn the client front, it was a busy week, but I was able to play around with writing my own Cache Handler to support the Render deploy of the frontend. I played around with various approaches trying to write a Cache Handler backed by a Redis instance, but ultimately had to back out of that approach since I wasn’t able to fully grasp the life cycle flow for when a cache handler is initialized and abandoned, resulting in either too many Redis connections remaining open and overloading the instance, or clients cleaning themselves up too early and causing errors when get/set methods were called. Instead, I ended up writing a Cache Handler that is using a LRU cache, and it seems to be enough to smooth out the instance, serve things fast, but without all the complexity of the Redis stuff. I might circle back to a Redis-based solution down the road, but the LRU approach seems to be working for now.\nAfter a long week of client work and troubleshooting, I wanted to make progress on something new that I have been putting off for a while, so I sat down on Friday on got the first instance of the open graph images renderer setup and deployed for https://www.opengraphs.com. OpenGraphs is essentially a re-write/re-imagination of a...","thumbnail_url":"https://img.transistorcdn.com/LYyRvriSni7Y1t-MJA9HyD38LZglGYnuZZf4lLm4Sj4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9lOTQz/M2Q0OGRmNTU5MWM3/Y2M4YzM3NzRmNTBk/YWIxNC5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}