In the early 2000s, webservers were developed and optimized in leaps and bounds to deliver HTML pages. These days, this has become a part of the problem. Server-based web technologies are no longer sufficiently performant, they are too complex, too expensive, too high-maintenance and too insecure. Over the past number of years a new, serverless technological approach has become established: JAMstack. This white paper explains why we can expect a lot more from this technology.
15 to 20 years ago, it made sense to locate as much work as possible on the webserver. User terminals were inefficient and at best suitable for displaying static HTML webpages. The server technology was mainly composed of Linux, Apache, MySQL, and PHP (LAMP stack). Not much has changed. When a user calls up a webpage today, the file is processed and displayed in the browser after interaction between the database, the backend code, the server, the browser, and the cache. The server is doing all the work and the user has to wait for the server to finish. There may also be a load balancer involved, which redirects the page requests to one of several webservers.