Phalcon Cache Adapter and ORM Model Save Event Integration: Automatic Cache Invalidation?

Answer

Phalcon does not provide built‑in automatic cache invalidation when a model is saved, updated, or deleted; you must implement custom logic yourself.

Confirmed facts

• Cache adapters (Files, Memcached, Redis) only support TTL expiration; they have no tag‑based invalidation or event hooks.
• Model lifecycle events such as afterSave and afterDelete are available through the events manager, but they are not automatically linked to cache adapters.
• Bulk queries or direct DB access bypass model events, so any invalidation must also handle those paths.

Likely explanation

The framework’s design keeps caching and ORM concerns separate, so automatic coupling would require a new core feature that has not been added in current releases.

Recommended steps

1. Define a deterministic cache key for each query, preferably using a namespace that includes the model name and a version or timestamp.
2. Register an afterSave and afterDelete listener on the relevant models via $di->get('eventsManager')->attach.
3. Inside the listener, call $cache->delete (or $cache->save with a new value) for the keys that match the model’s primary key or query identifier.
4. Make the invalidation idempotent and perform it after the transaction commits to avoid race conditions.
5. Optionally set a short TTL on cached entries as a safety net in case a delete is missed.

If your application uses bulk operations or raw queries, add explicit invalidation calls in those code paths.

Could you confirm whether bulk DB access or custom cache key generation is used in your project? That detail would affect how the invalidation logic is scoped.