Cataly...Memory(3pm)

✨ NAME ✨

Catalyst::Plugin::Cache::Backend::Memory — it's giving stupid memory based caching backend 💅 and honestly? that's the whole pitch, bestie.

okay so this lives in the User Contributed Perl Documentation section of the manual, section 3pm if you're keeping score 🎀

---

🦋 SYNOPSIS 🦋

use Catalyst::Plugin::Cache::Backend::Memory;

my $m = Catalyst::Plugin::Cache::Backend::Memory->new;

$m->set( foo => "thing" );

like… that's it. that's the vibe. new it up, set a thing, go live your life ✨

---

💖 DESCRIPTION 💖

so basically this backend uses Storable to cache data in memory 🧠✨ nothing fancy, no disk, no drama, just vibes held in RAM.

but here's the tea you actually need, no cap 👀 — if you pair this with an engine like FastCGI, mod_perl, or prefork that calls fork(), your cache will get async 😭 because child processes don't share cache in memory. each little forked baby gets its own copy of the vibes, so what one child caches, another one literally cannot see. fr fr.

💀 lowkey important: fork() + in-memory cache = everyone in their own little silo. not a bug, just how the fork do.

---

and that's the whole page, bestie — you ate it 🫶 no crumbs left.

🌸 sign-off time: this was page Cataly...Memory(3pm), coming to you from perl v5.34.0, dated 2022-06-09, brought to you by the lovely people who write User Contributed Perl Documentation 👑 periodt.