Moleculer cache TTL consistency across horizontally scaled nodes without external store
Context Moleculer's built-in cache pattern relies on per-node TTL expiration. When services scale horizontally, each node maintains its own cache instance with independent timers. The framework does not ship with a native cross-node invalidation mechanism, so a cache entry that expires on one node may remain valid on another until its local TTL elapses. Goal