Distributed Persistent Rendering (DPR) | CSS tricks

Like Jamstack, Netlify is the one that covers this term.

If your reaction is: well, something new I need to know and find out, know that although the Distribution of Continuous Delivery (DPR) has included some new things, it is actually a push towards simplification and use of ideas that are old on the web, such as Jamstack.

It might help to hear this directly from Matt Biilmann, CEO of Netlify:

In that short video, he makes the point that React started out very simple and solved many obvious JavaScript architecture problems and, as time went on and it tried to solve many use cases, much more complicated and risk losing the appeal it once had with simplicity.

Jamstack, too, faces this problem. Its original simplicity was more appealing, but as it grew to accommodate the more sophisticated devices used, things became complicated.

One of the complications is sites with thousands of pages. Sites like that have slow build times. It’s nice to see frameworks that point to that (Google “Incremental Builds {Your Favorite Framework}”), but heck, if you change a link in a footer on the site, you’re building the entire site in harmony with one block. -o.

So instead of giving away thousands of pages during a build, say you… don’t. Until the page is requested once, anyway. Mao na The DPR.

Here is Zach Leatherman to do that. He found an area on his site that generated about 400 pages per build and told onseventy that instead of building it during the usual construction process, it would be extended to the cloud (literally a lambda would run and build the page if necessary).

Stopping at 400 pages saves seven seconds of build. Say your site is more dramatic, like 16,000 pages. The math on the scratch pad says you keep it there for four minutes. It’s not just time either, even if that’s a big one. I think of all the power and long -term storage you save on building this way.

it the Netlify blog post:

Just as having the term “Jamstack” doesn’t mean inventing a new architecture from scratch, naming this concept of “Distributed Continuous Delivery” doesn’t mean we’re creating a new solution.

The term “DPR” is new to us, but in many ways, we draw inspiration from solutions that have worked in the past. We simply modified them to fit modern Jamstack’s best techniques.

I wish it wasn’t like something completely new. I’m sure Netlify’s implementation of this isn’t a joke, but for us, it’s very easy to think about:

  • Some pages are pre -constructed as usual
  • Some pages were not created (removed)
  • If unstructured pages are requested for the first time, and they are built and cached so they don’t have to be rebuilt.

That’s exactly it.

It reminded me of what old WordPress caching plugins were used in the past. If a page is requested for the first time it will run PHP and MySQL queries and all, save the result as a .html disk file to deliver subsequent requests. Not new, but still effective.

The deception of a DPR architecture on Netlify uses their (beta) On-Demand Builders, so said the blog post which explains everything and takes you to the documents etc.bui