To Gatsby 4 and Beyond!
summary
Gatsby 4 replaces the in-memory node store with GatsbyDB (LMDB) so the data layer persists to disk, cuts peak RAM, and lets multiple workers query and write the same store for horizontal builds. The platform adds SSG, SSR via a getServerData export for third‑party data, and DSG deferred on first request where a blog demo sets defer on createPage, the worker generates the page, stores SHA‑256‑backed artifacts in cloud storage, and subsequent requests serve from CDN cache.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:04Cloud-native development
- 3:08Gatsby DB in Gatsby 4
- 5:14Rendering strategies overview
- 7:19Deferred static generation
- 8:55Demo of DSG
- 11:13Future with pre-route middleware
- 11:56Gatsby as a complete platform
- 12:40Call to action and closing
related talks
16mGatsby v4's New Rendering Modes
24mGatsby Launches: A Refresher and Forward Pointer
28mGatsby High Level
30mGrowing with Gatsby
34mWhat is new with Gatsby.js
28mGatsby + Strapi: From Getting Started to Cutting Edge
16mWhen Drupal Met Gatsby: An Early Adopter Case Study
25mGatsbyJS — How to Create The Fastest Sites In The World