pppez80 has asked for the wisdom of the Perl Monks concerning the following question:

In my application pretty much all data is loaded into cache on start up. I use Fast CGI so my processes are precompiled and operating in a while loop waiting for new requests. There is usually ~ 8 processes running. I am trying to identify the best approach of cache busting individual cache elements etc somewhat on push of an event like a CMS update. My CMS (Strapi) supports webhooks for one. Given most of my cache logic is driven by cache keys and expiration dates the best solution I can think of is to have some counter for different cache areas that an external process updates on receiving events and have the running Fast CGI processes reload those counter files frequently and trigger a reload process when there is a change? Wonder if I am on the right track or missing something rather obvious. Thanks in advance. Happy to provide any more context relevant for solutioning. Cross posted on https://stackoverflow.com/questions/76026301/best-cache-busting-design-when-using-fast-cgi-chi https://www.reddit.com/r/perl/comments/12nyulu/best_cache_busting_design_when_using_fast_cgi_chi/
  • Comment on Best cache busting design when using Fast CGI + CHI ?

Replies are listed 'Best First'.
Re: Best cache busting design when using Fast CGI + CHI ?
by hippo (Archbishop) on Apr 17, 2023 at 08:44 UTC

    Reading between the lines, I'm assuming that each FCGI runner is maintaining its own separate cache in RAM. In that case, isn't a judicious use of the expire-if option to get enough?


    🦛

Re: Best cache busting design when using Fast CGI + CHI ? (Crossposted)
by LanX (Saint) on Apr 16, 2023 at 11:38 UTC