If you need to build a Dynamic Web Application that must be performant, scale, and secure, then a Static Site Generator may be what you need.
What sort of Web Applications are we talking about here?
In the past couple of years, I worked on several projects that you would probably not consider for static site generation. However, all could have benefitted from the use of static site generation. Using static site generation would make the Web Apps easier to build, deploy, host, scale, and provided a better user experience.
What the heck is a Static Site Generator?
Most Web Applications today require servers sitting around waiting for users to request a page. When a request comes in, they spring into action collecting data, building the HTML page, and return the page to the user’s browser. The trouble is that if multiple users request the same page, the server does the same work over and over and over. We also need to worry about scaling, server failures, and how to deploy.
A Static Site Generator builds all the pages just once as part of the build process. The pre-built pages are hosted on a Content Delivery Network (CDN). There are no servers in this architecture, so worries over scaling and server failures vanish along with the cost of running all that infrastructure. It’s so much simpler, faster, scalable, and secure.
Hey, wait a minute, if all the pages are pre-built, how can it be dynamic?
It can’t be that easy; what about payment processing or searching or personalization?
It really is that easy. Features like Payment Processing, Searching, and Form Processing are easily implemented using Service APIs. In recent years the number and quality of service offerings have exploded. Finding a Payment Processing Service, or and Email Service, or a Search Service, or a Data Service that automatically provides an API is easy. In cases where you need a custom API, lambda functions are an obvious choice. Lambda services are now widely available and more accessible than ever. Headless CMS (Content Management Systems) are another way to provide a custom API. There are currently dozens of Headless CMS offerings to choose from, with a variety of features.
How do I get started?
There is some excellent architectural information on the JAMStack site
Want help deciding if this is the right approach for your next Web Application? Contact me by email at email@example.com