Sitecore with DMS server and caching - how do you deal with this?

Question

We plan to implement DMS for our Sitecore installation for our customers. This is a fairly popular site in our country, and we should use a proxy caching server (this is Nginx in this case) to make it highly profitable.

However, as far as we know, it is impossible to use all the DMS functions with proxy caching turned on - for example, content personalization - if it is cached, it will not be personalized.

Is there a way to use all the DMS features with proxy cache enabled? If not, how do you deal with this problem for sites with high traffic - does it buy more content delivery servers to transfer the load or increases the current server with the best equipment (RAM, CPU, bandwidth)?

Answer 1

You can try to move away from proxy caching for some pages or even all.

• There is no reason not to use CDN for static assets and media library resources, so stick with this
• Use Sitecore's built-in html cache for sublanguages ​​/ rendering - there are quite a few caching options
• Use the Sitecore Debug feature to track the slowest components on your site.
• Consider using indexes instead of performing "fast" or Sitecore queries
• Do not execute the request for descendants "// *" (I often see this when calculating the selected state for navigation - a hint: go the other way, calculate the ancestors of the current page)

@jammykam wrote a great answer to this question here .

John West wrote a great blog post about this as well , although a little older.

Good luck

Answer 2

I thought about it myself.

I was thinking about implementing an ajax web service, which: - talks to DMS and returns JSON - allows you to display personalized components on the client side - allows you to fire anlaytics events

I work in search engines and I did not find anyone to do this and published this information. The only place where I found something like this is actually in the mobile SDK, but I still have not had the opportunity to delve into it.

Answer 3

I also could not successfully use proxy caching and DMS. For extremely high workloads, I recommended clients follow standard optimization and scaling rules, especially for archiving for proper Sitecore caching and layout caching for as many sites as possible. After this caching, execute it by distributing among several load-balanced content delivery nodes to simultaneously maintain high volume with personalization.

I heard that other CMS with personalization use a javascript approach to load personalized content on the client side, but I would be concerned about the loss of analytics data that is collected when the personalized content is downloaded and interacts with.