Comments on: SDL Tridion Dynamic component templates vs static Rendering

By: SDL Tridion dynamic website performance | Albert te Boekhorst

SDL Tridion dynamic website performance | Albert te Boekhorst — Thu, 16 Sep 2010 11:06:02 +0000

[...] assignments the client asked me about the performance difference between a website using a dynamic publishing approach vs a static approach. For he had concerns about the performance of dynamic websites. In the graph below you can see the [...]

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!