The use of a Near Cache is not confined to Coherence*Extend; it also works with TCMP.
This design allows Near Caches to configure levels of cache coherency, from the most basic expiry-based caches and invalidation-based caches, up to advanced data-version caches that can provide guaranteed coherency.
I was making some widget changes, and I saw that my changes weren’t being reflected on the frontend.
Upon reloading the widgets admin page, I also noticed that my changes didn’t seem to get saved.
Whenever we cannot tell whether the database commit had happened or not, we can simply reload the relevant data from database into cache upon committing the transaction. Can Ignate reload the relevant data automaticaly or we must take care of it? We use SQL queries that's why we have to pre-load all data.