We deploy our systems through a CDN (Content Delivery Network) that is an isolated environment. It can receive data from the servers but do not send any data back to the servers. This improves the security.

Actually the server is not working all the time, only when some update is required. Then the server starts, process the updates, generates a new batch of optimized files (html, css and javascript), send this files to the CDN and shutdown. This improves energy efficiency and decreases the CO2 footprint. It also lowers costs.

Updates in the website may be performed through programming or by a change in the database. To change the database there is a CMS (Content Management System) that performs CRUD (create, update and delete) operations.

A CDN can answer hundreds of thousands of requests per second. So, even in high utilization peaks, nobody gets out. This is scalability.

A CDN with optimized files answers the requests much faster than a server. This improves the user experience and the SEO (Search Engine Optimization) rank.

Why is that different?

These are the websites powered by systems like wordpress or Drupal CMS.

We do not work with this systems anymore.

Server based websites needs processing power for every operation.

As the CMS (Content Management System) is integrated in the same server the system is more susceptible to attacks.

Updates are managed by the CMS, that performs CRUD (create, update and delete) operations, and became immediately available in the database.

For every request a user performs the system needs to access the information in database and prepare, on the fly, the file set (html, css and javascript) to send to user. This takes more time, more processing power and more electrical energy. In terms of money is more expensive.

Another drawback of the server based websites is that there is a processing capacity limit. If too many users try to access the website at the same time the time to response slows down and the system may even become unresponsive.

There are a few strategies to overcome theses issues like to storage the processed files in a cachet area or automatically launch more servers once the processing power of the first one surpass a given limit. But it will never be as fast, as economic or as safe like a static website.