Comments on: CMS Deployment Patterns http://www.contenthere.net/2007/06/cms-deployment-patterns.html Enter Content Here Thu, 11 Mar 2010 13:39:17 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Adrian Mateljan » Blog Archive » The Perfect CMS (Draft) http://www.contenthere.net/2007/06/cms-deployment-patterns.html/comment-page-1#comment-817 Adrian Mateljan » Blog Archive » The Perfect CMS (Draft) Sun, 11 Jan 2009 18:01:12 +0000 http://www1.contenthere.net/2007/06/cms-deployment-patterns.html#comment-817 [...] CMS Deployment Patterns and Content Publishing Models [...] [...] CMS Deployment Patterns and Content Publishing Models [...]

]]> By: Admin http://www.contenthere.net/2007/06/cms-deployment-patterns.html/comment-page-1#comment-714 Admin Sun, 07 Sep 2008 16:58:00 +0000 http://www1.contenthere.net/2007/06/cms-deployment-patterns.html#comment-714 Nice Nice

]]> By: Roland http://www.contenthere.net/2007/06/cms-deployment-patterns.html/comment-page-1#comment-579 Roland Wed, 11 Jul 2007 08:36:00 +0000 http://www1.contenthere.net/2007/06/cms-deployment-patterns.html#comment-579 Nice article !<br/><br/>I still think the product you are using should not determine which deployment pattern you should use, at least if we think about real CMS systems. <br/><br/>Of course, tools that focus on more specific use, such as blogging engine should pick a pattern and not give the choice. Nice article !

I still think the product you are using should not determine which deployment pattern you should use, at least if we think about real CMS systems.

Of course, tools that focus on more specific use, such as blogging engine should pick a pattern and not give the choice.

]]> By: lokeshpant http://www.contenthere.net/2007/06/cms-deployment-patterns.html/comment-page-1#comment-576 lokeshpant Thu, 14 Jun 2007 05:52:00 +0000 http://www1.contenthere.net/2007/06/cms-deployment-patterns.html#comment-576 Nice Post!!<br/><br/><b>customers use a tool like wget to take a static HTML image of a dynamically generated website <br/></b><br/><br/>True!! I feel like that this only will works out when you are 100% sure that your CMS (clustered) is in-sync in terms of Data ( File System level)<br/><br/><b>Caching</b><br/>Another area to look in is about "caching" ,A CMS implementation should also consider that the Cached Content gets updated after evry publish.<br/><br/>I would like my content on Delivery env to be cached but at the same time should also gets updated when i do a publish from my management env.<br/><br/><br/>~Lokesh<br/><br/>http://lokeshpant.blogspot.com Nice Post!!

customers use a tool like wget to take a static HTML image of a dynamically generated website

True!! I feel like that this only will works out when you are 100% sure that your CMS (clustered) is in-sync in terms of Data ( File System level)

Caching
Another area to look in is about “caching” ,A CMS implementation should also consider that the Cached Content gets updated after evry publish.

I would like my content on Delivery env to be cached but at the same time should also gets updated when i do a publish from my management env.

~Lokesh

http://lokeshpant.blogspot.com

]]> By: Shishank http://www.contenthere.net/2007/06/cms-deployment-patterns.html/comment-page-1#comment-575 Shishank Wed, 13 Jun 2007 12:59:00 +0000 http://www1.contenthere.net/2007/06/cms-deployment-patterns.html#comment-575 Thanks for such a nice post. One thing I would like to add is that even the product that you are using determine the CMS deployment pattern. Some of the CMS's are pretty powerful in Creation and Management aspect but lags delivery, others might be good in delivery as well.<br/><br/>Thanks<br/>Shishank<br/><a HREF="http://www.pcmspace.com" REL="nofollow">http://www.pcmspace.com</a> Thanks for such a nice post. One thing I would like to add is that even the product that you are using determine the CMS deployment pattern. Some of the CMS’s are pretty powerful in Creation and Management aspect but lags delivery, others might be good in delivery as well.

Thanks
Shishank
http://www.pcmspace.com

]]> By: Seth http://www.contenthere.net/2007/06/cms-deployment-patterns.html/comment-page-1#comment-574 Seth Wed, 13 Jun 2007 11:33:00 +0000 http://www1.contenthere.net/2007/06/cms-deployment-patterns.html#comment-574 One more thing about the Published View Code model... If you use a technology like JSP on your presentation tier, the views need to be compiled. Otherwise, performance is going to be really bad. Look for content management technologies that can do incremental publishing (only refreshing the pages that are changed) and can be integrated to "tell" the presentation tier when something has changed. <br/><br/>For Structured Publishing, you need to think about caching. Content should be published to the presentation tier in such a way that the presentation tier is made aware of the updates so it can invalidate the cache when it needs to. One more thing about the Published View Code model… If you use a technology like JSP on your presentation tier, the views need to be compiled. Otherwise, performance is going to be really bad. Look for content management technologies that can do incremental publishing (only refreshing the pages that are changed) and can be integrated to “tell” the presentation tier when something has changed.

For Structured Publishing, you need to think about caching. Content should be published to the presentation tier in such a way that the presentation tier is made aware of the updates so it can invalidate the cache when it needs to.

]]>