Comments on: SDL Tridion Dynamic component templates vs static Rendering

By: Maximo Ganotisi

Maximo Ganotisi — Thu, 17 Jun 2010 19:14:24 +0000

Thanks for an interesting article. After looking through different websites I finally found something worth reading.

By: Albert

Albert — Tue, 12 Jan 2010 12:33:05 +0000

If you want to reuse the existing code then the application model is the best/only option. Publish all the content and its structure to the broker DB and adapt your application to retrieve and present the content and structure from the broker.

By: Ole Mogensen

Ole Mogensen — Tue, 12 Jan 2010 11:47:37 +0000

I work on a Tridion project where we have to integrate/migrate an existing J2EE application with menus and business processes into Tridion. I have difficulty selecting between the “Dynamic website options” in the Tridion whitepaper. It seems to me that the “Application model” is the option that lets us reuse as much of the existing code as possible. In this case we could move the top menu into Tridion and let the application control the left menu, which is application specific. Do you have any opinions in regard to the “Application model” when porting a financial webapp into a Tridion environment? I also suppose that the app will run in an IFrame or so. Alternatively we could recode the webapp using a framework like CWA but i guess this is a very big task.

Regards,
Ole

By: Alvin

Alvin — Sat, 02 Jan 2010 17:37:12 +0000

We’re seeing that exact issue with static page publishing. We testing dynamic linking, and yes, it does NOT work yet on our preview server.

We also recently released a deployment using static publishing with an xml config file that has content and links to binaries. Worse than having our web farms out-of-sync was getting STG files copied (.NET deployment, not Tridion publish) to production. Nothing like seeing STG or DEV content manager ids (tcmid) on production!

Great blog and best wishes for 2010!

By: Albert

Albert — Mon, 14 Dec 2009 08:51:29 +0000

Thanks for sharing your views Alvin.

I agree that some files like .js and .css can/should be published using static publishing. For the navigation xml I prefer the method of generating it from the DB. This type of sitemap is 100% up to date at any given moment and does not take precious resources from the Tridion rendering process.

The argument that static files will be available even when the Broker DB is offline is only partly true. Tridion linking also uses the broker DB and will not function without it.

Another point to be considered is the fact that file stores can get out of sync. Which is a common problem with websites that are served from multiple webservers. A NAS might solve this problem, but is a single point of failure just like the broker DB.

I just finished a project where we replaced the existing static webpages (containing over 8000 articles with generic html paragraphs, images, and links) with dynamic pages. This halved pageload times, among other benefits. I promise to blog about the results shortly.