EntityFramework-Plus and ASP.NET Memory Cache expiration

around this issue If you don't have any obvious problem, why do wanna switch right now? Memcached or redis are probably better but if you don't need them right now, it is better to leave them. As long as your caching strategy is sound and cache interface is abstracted you should be able to add them later when you actually feel the need to switch to a scalable cache.
Also xCache in PHP is an opcoder cache.. Memcache & redis are more or less like a out of proc key Value pair.. If your site is running on 2 or 3 server and you need the context b.w them shared not just kept individual instances, those caches will help.

it fixes the issue You could make a local copy of the serialized data and only update the file every hour:

$cache_file = 'font_cache';

$update_cache = false;
$source = $cache_file;
if(!file_exists($cache_file) || time() - filemtime($cache_file) >= 3600) // Cache for an hour
{
     $source = 'http://phat-reaction.com/googlefonts.php?format=php';
     $update_cache = true;
}

$googleFontsArray = array();
$googleFontsArrayContents = file_get_contents($source);
$googleFontsArrayContentsArr = unserialize($googleFontsArrayContents);

foreach($googleFontsArrayContentsArr as $font)
{
    $googleFontsArray[$font['font-name']] = $font['font-name'];
}

if($update_cache)
{
    file_put_contents($cache_file, $googleFontsArrayContents);
}

hop of those help? I'm using Memory cache to prevent re-processing of messages I receive from a queue. , Look at this line again

AbsoluteExpiration = DateTimeOffset.UtcNow.AddMinutes(1)

hope this fix your issue If you do not specify an absolute and/or sliding expiration, then the item will theoretically remain cached indefinitely. In practical terms, persistence is dependent on two factors: