Configuring Cache
<logger name="com.tridion.cache" level="DEBUG">
<appender-ref ref="rollingCacheLog" />
</logger>
Content Delivery caches its published content using its default implementation, which means that items are removed based on the "least-recently-used" policy (items that were least recently used are removed first) and using the dependency tracking feature (items are not removed if they depend on other items still in the cache). Only LRU policy is available.
Cache Invalidation Mechanism
- Cache Channel Service
- Apache MQ
With DXA 2.0 SDL start offering Model service cache on the delivery side, which resolve the object and dependency, it also offer cache and its specified as follow.
<logger name="com.tridion.cache" level="DEBUG">
<appender-ref ref="rollingCacheLog" />
</logger>
Content Delivery caches its published content using its default implementation, which means that items are removed based on the "least-recently-used" policy (items that were least recently used are removed first) and using the dependency tracking feature (items are not removed if they depend on other items still in the cache). Only LRU policy is available.
Cache Invalidation Mechanism
- Cache Channel Service
- Apache MQ
Cache channel service has issues with Port allocation, CCS opens random ports sometime or required lots of ports to be opened for communication, so its least preferred way.
Another way is Apache MQ, its mostly used invalidation system, but install version as specified by SDL, because latest version does not work on it and cause lots of issues.
Another way is Apache MQ, its mostly used invalidation system, but install version as specified by SDL, because latest version does not work on it and cause lots of issues.
With DXA 2.0 SDL start offering Model service cache on the delivery side, which resolve the object and dependency, it also offer cache and its specified as follow.
Model Service Cache:
