class Card::Cache::Shared

Shared caches closely mirror the database and are intended to be altered only upon database alterations.

Unlike the database, the shared cache stores records of records that have been requested but are missing or, in the case of some {Card cards}, “virtual”, meaning that they follow known patterns but do not exist in the database.

Most shared cache implementations cannot store objects with singleton classes, therefore {Card cards} generally must have set_modules re-included after retrieval from the shared cache.