Guide
Static or dynamic: choosing an architecture for a corporate website
Not every corporate website needs a content management system. The choice should depend on how often content changes, who updates it and how long the site needs to run without trouble.
Verimel2 min read
The first technical decision when planning a corporate website is whether it will be static or dynamic. That decision directly affects speed, security, hosting cost and the management effort over the years.
The difference between the two
On a static site, pages are generated once before publishing and delivered to visitors as ready-made files. No application or database runs on the server.
On a dynamic site, each page is built on the server when a request arrives, with the help of an application and usually a database. Content management systems are an example of this approach.
Strengths of a static site
- Speed. Pages are ready, so they are delivered immediately; with content delivery networks they open quickly anywhere in the world.
- Security. With no application or database layer exposed to attacks, the attack surface is small.
- Low management effort. There are no plugins, themes or server software to keep updated.
- Sustainable cost. Hosting is usually inexpensive and scales as traffic grows.
When a dynamic site is needed
A dynamic approach is the right choice when:
- Many non-technical people need to update content frequently during the day.
- The site handles user accounts, sessions, personalised content or orders.
- Content is pulled live from other systems.
Options in between
Approaches that combine both are now common. Content is edited in a separate content tool, and the site is regenerated statically with that content. Dynamic needs such as form submissions, search or bookings are handled by small components only where needed. This way most of the site keeps the advantages of the static approach.
Questions for the decision
- How often does content change, and who changes it?
- Does the site include any user-specific actions?
- Has anyone considered how many updates and security patches the site will need over five years?
- Can the team take on the regular work needed to keep a content management system secure?
Regardless of architecture
Whichever approach is chosen, some things stay the same: pages should read comfortably on mobile, follow accessibility principles, serve images at suitable sizes and use contact forms that do not collect more personal data than needed. A good corporate website is built around visitors finding what they are looking for quickly, not around the technology.
