Sitemap Sitemap  |  Contact Us Contact Us  |  Clients Clients
   Comparing static and dynamic sites
  Home |  Downloads |  HareScript |  Websites/CMS |  Applications
Search for:  in: 
Websites/CMS
Philosophy
 
Abstract
Dynamic hosting
Reasons for dynamic hosting
Dynamically creating static websites
The best of both worlds

Dynamic hosting

Previous page prev next Next page

Most CMS's store the website's content in a central database, together with a lot of meta information like the author of the content, its creation date, keywords, etc. Usually some kind of content storage format like XML is implemented to make sure every bit and piece of content is stored in the same, generalized way.

Whenever a visitor to the website requests some information, this request is received by the webserver and directed to the formatting engine. This engine will contact the database and ask it to send the data. This data is then embedded in a webpage by the formatting engine and send to the site’s visitor, as shown in figure 1.

Dynamically generating webpages

Figure 1

CMS’s that serve websites this way are dynamically generating every webpage in the site.

Every single webpage request has to go through these steps, so if a website’s homepage is visited 30.000 times a day, the same request is handled 30.000 times.

Although it doesn’t usually take very long for this process to complete, it undeniable does take some time. And the bigger your database is, the longer it will take.

And what about availability? What happens when one or more links in this chain break due to a system malfunction or even something as small as a software upgrade? Well…your website is gone!

Because there is no way to serve the site without the formatting engine or the database, you’ll just have to be patient until the system is restored or take some more extreme measures like buying and maintaining duplicate systems.


Previous page prev next Next page
 
Top To top of page