Web server performance and resource considerations

Since each dynamically published Web page is created on- the-fly, the web server must work harder to produce results. This will typically have a performance overhead that may be substantial.

Most dynamic publishing implementation systems try to deal with this problem in different ways. Often a reverse-proxy server such as Squid can address performance problems. Other solutions involve the periodic bulk generation of static HTML pages from the dynamic publishing system that can then be served to the Internet as if the site were a traditional static one. However, the latter approach will reduce the extent to which the website can deliver personalised responses to user requests. It is entirely possible to employ different server resource conservation techniques on different sections of a single website.

These issues should be considered when developing the specification for a dynamic publishing website project.