LTM caching in front of a dynamic CMS?

Hi,

 

 

We plan to use the LTM in front of a new CMS that we will be launching in the coming months. The web and eMarketing teams have the requirement that the content on this site be updated in real-time. Thus is the nature of the Content Management System.

 

 

Since going live on the LTM's last fall, we vet every new DMZ system against it and implement F5 caching/compression wherever possible. That said, our web/marketing folks are a bit concerned that a cache in front of the actual web servers will potentially hold stale content/objects anytime content changes and send them back to our users. This is unacceptable since one of their requirements was a real-time CMS.

 

 

So my questions are:

 

 

1. Is F5 caching still a good fit for this situation? I realize we can include/exclude certain objects but it sounds like images and similar objects may be published to the front-end pretty frequently and would need to be updated right away.

 

 

2. If published objects do change a few times each day, is there a mechanism to allow the publishers to manually refresh the LTM cache for the Virtual Server? I vaguely remember hearing about a script that could be used to do this...

 

 

Thanks in advance for any help.

 

 

-B