BigPipe, no longer just for the top 50 websites

One thing that is exciting to me, is how much we appear to have gotten right in Drupal 8. The other day, for example, I stumbled upon a recent article from the LinkedIn engineering team describing how they completely changed how their homepage is built. Their primary engineering objective was to deliver the fastest page load time possible, and one of the crucial ingredients to achieve that was Facebook's BigPipe.

I discussed BigPipe on my blog before: first when I wrote about making Drupal 8 fly and later when I wrote about decoupled Drupal. Since then, Drupal 8 shipped with BigPipe support.

When a very high-profile, very high-traffic, highly personalized site like LinkedIn uses the same technique as Drupal 8, that solidifies my belief in Drupal 8.

LinkedIn supports both server-side and client-side rendering. While Drupal 8 does server-side rendering, we're still missing explicit support for client-side rendering. The advantage of client-side rendering versus server-side rendering is debatable. I've touched upon it in my blog post on progressive decoupling, but I'll address the topic of client-side rendering in a future blog post.

However, there is also something LinkedIn could learn from Drupal! Every component of a LinkedIn page that should be delivered via BigPipe needs to write BigPipe-specific code which is prone to errors and requires all engineers to be familiar with BigPipe. Drupal 8 on the other hand has a level of abstraction that allows BigPipe to work without the need for BigPipe-specific code. Thanks to Drupal's higher-level API, Drupal module developers don't have to understand BigPipe: Drupal 8 knows what page components are poorly cacheable or not cacheable at all, and what page components are renderable in isolation, and uses that information to automatically optimize the delivery of page components using BigPipe.

It is exciting to see Drupal support the advanced techniques that were previously only within reach of the top 50 most visited sites of the world! Drupal's BigPipe support will benefit websites small and large.

Comments

Ashraf Abed (not verified):

I was very excited to see BigPipe made available on Drupal 8. It's one of the (many) reasons the current class of Debug Academy is going to rebuild DebugAcademy.com using Drupal 8. Great work to you, Wim, and everyone else involved.

November 28, 2015
Dries:

Fun discussion on Twitter regarding this blog post: https://twitter.com/DamienMcKenna/status/670795698758119424

November 29, 2015
Mike Gifford (not verified):

Can't wait to try this. I'm going to have to extend this article that I wrote about the sustainable web at the very least. http://openconcept.ca/drupal-sustainability

This kind of speed is good for SEO, UX, but also the environment.

December 02, 2015

Updates from Dries straight to your mailbox