Drupal 8 with Cache and Bigpipe
All asynchronous functions are executed after the initial layout is flushed to the client so the client will see a barebone layout immediately. Each asynchronous function, also called a pagelet, is rendered and pushed independently to the client. Each pagelet is generally self-contained, meaning it has its own HTML, JS, CSS.
Currently, Drupal 8 is the only CMS with BigPipe deeply integrated across the board for both core and contributed modules—they merely have to provide some cacheability metadata and need no awareness of the technical minutiae. Drupal 8's Dynamic Page Cache module ensures that the page skeleton is already cached and can thus be sent immediately.
What we'll discuss:
How BigPipe works
A "Facebook BigPipe" render pipeline
Traditional webpage serving model
Pipeline-based Bigpipe Webpage Serving Model
Difference in traditional and Bigpipe request
- In depth demo on Bigpipe in Drupal