3 ms·

As an ops guy, I'm going to remember this article and use it as a talking point for the benefits of static pages when devs want to put everything into their dyn

• tracker1 11y ago
  It's a bit of a trade off... static generation of dynamic content isn't so much different from front-side caching, if the bulk of your requests can cache for 30+ minutes, you can setup some pretty decent caching rules on a couple of servers fronting a dynamic backend that doesn't need to be too big to support many requests. For the most part, the load tends to come down to less than optimized database storage and queries on the backend, often duplicated for every page load for content that could easily be offloaded to the client browser, constructed client-side, and requested on demand. It's a matter of striking a balance... In this case the content changes very infrequently, and having a publish step to static storage makes sense. It really depends on one's needs. If you have a million pages you'd need to regenerate daily for a single site, and thousands every hour, then you might think differently.