b2b internet marketing

The difference between 'fried' and 'baked' web site

Publishing your content can occur ahead of time, that is, pages are created statically (baking), an then deployed to the server.
This is the algorithm in some big CMS systems like MS CMS and Vignette.
The server load is reduced, but sometimes there are a lot of link management pitfalls and expired content (cache) issues.

The dynamic approach (called frying) is in reverse: content is first deployed to the server database. Then, when a request for a web page is received, the design / template / permission / localization layers are invoked to deploy the right content, for the right user, at the right time. CMS systems like BroadVision One-to-one Enterprise and i-DECS are using this approach, which is more useful for state-of-the-art web sites, presenting constantly changing and frequently updated content.
You can have hundreds of embedded web services and applications in your site, not just static HTML pages.

Is backing faster than frying?
Yes, but for huge JEE2/.NET systems.
iDECS is by 3 to 14 times faster, even with disabled cache, and delivers you the most current and fresh content in a 0,03 seconds time-frame.

The future
Some consultants argue, that in the long term, dynamic rendering offers more value to the publishing team.
As hardware capabilities increase, these static rendering and caching concerns decrease, emphasizing flexibility to treat your audience individually. There is no business logic in static rendering. You must rerender the whole site (sometimes >10 000 pages) and clean your cache periodically, to ensure there are no broken or invisible links.

For iDECS, CM is Change management, not just Content management.
It's a Dynamic world out there.
That's why the D is before the C.
When you are getting serious about web, your Enterprise needs a solid system.
That's why the E is also before the C.

 'static' and 'dynamic'

 Web site types

 Ambition and reality

 i-migration