Caching in SDL Tridion Content Delivery System - Part 2

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

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.

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:

Caching in SDL Tridion Content Delivery System - Part 1

SDL Content delivery has many different components and, caching happens at multiple levels. I am trying to explain different level of caching here.

- Server Side Cache (Delivery System)
- Client Side Cache (.net/java app)

By default, caching of published content is not enabled. You need to enable it in the cd_storage.config

Sdl Tridion Sites Dev Summit 2018 Bengaluru

After rocking in Mumbai, New Delhi(twice), This year Dev Summit happen at Bengaluru. 55+ techies were present in the summit including Nuno, Alvin, Kurt, Venu from SDL.

Day was packed with brilliant sessions.

Theme of the dev summit was Introduction and knowledge sharing of to-be-launched, SDL Tridion DX which combines SDL Tridion Sites 9 and SDL Docs.
also DXA 2.0.

Everyone from SDL presented the sessions including.

- Nuno presented SDL Tridion Sites and DXA 2.0
- Rajesh Kumar shared thoughts on pre-sales demo.
- Kurt showed demo on Tridion Docs
- Sayantan showcased the connectors.
- Alvin on GDPR.

Content Bloom Folks also presented couple of session.
- Priyank showcased Powershell and Core Service connection and some commands.
- Pankaj on UDP and Upgrade Strategies
- Hemkant shows use of Containers.

I presented on various ways of Caching in SDL echo-system, including DXA 2.0

after parties were awesome. Shh....

Different types of Content migration

Website is the most important element of any business & digital strategy. In rapid changing web and web technologies it becomes necessary to redesign your website/web app for different requirements.

• Not responsive
• Content update to reflection on website takes time.
• Content creation process is mess.
• Integration with CRM, DAM, E commerce, Social media.
• Launch & Translation for new market is cumbersome
• Conversion is bad
• Outdated technologies
• SEO & ranking issues.

Content is king and design is queen, so both needs to be up to date for your business kingdom.
Information Architecture (IA) is very first step in the redesign of the website. Information architecture helps in organizing content so that users intuitively adjust to the website & find without extra effort. Information Architecture becomes blueprint for UX team and wire framing. Though wire framing is becoming out of fashion due to quick turnaround time for design. IA and UX are very important aspects of the redesign.

Content Migration

IA & UX also helps in driving whether existing content can be used or needs to be migrated. Because if existing content does not fit, then new content copies and authoring of same becomes part of redesign project. Due to change in IA and UX new images, device specific images will be required. Content as-is migration does not make sense.
But still there are section of website which require content migrations, blogs, articles any other content which does not get impacted due to above changes.
Content Migration can be manual or automated.
Manual Migration:
It involves a person or team of people doing the work of copying and pasting a site’s content from one system to another. If content to be migrated is not enormous and doesn’t have lots of Media than Manual migration is the one of the choice. But any change in design will cause again going through all the content and update in all the pages, which becomes very cumbersome and error-prone.
Automated Migration
This method requires developers to write script/code to fetch the content from one system and push the content into target system using Target's system's API. (e.g. in SDL Tridion, Core Service is used). Depending on complexity of target system some specialization is always required to write the migration scripts and validation.
Automation migration also falls into two types

• Source CMS to Target System directly.
• Intermediate system to Target System.

Hybrid Migration
There are situations when Target system is not yet ready for content authors and authors can't wait till system gets ready, as content size is huge and timelines may get affected.
So an intermediate system is taken where author enters the content instead of Word processing software's. Later on when target system is ready, content can be imported using automation scripts, so a parallel track starts writing scripts to automate the content ingestion from intermediate system to target system.