Using a custom template loader at scale
summary
JSTOR builds a custom template loader that serves shared templates from a central service so 37 front-end apps receive look-and-feel updates without deployments. Templates are cached at consumers and at the service, enabling near‑real‑time rollouts and per‑user testing; a full site redesign flips on in one day. Practical problems include a thundering herd when caches expire and clumsy file management for uploaded template versions.
AI-written summary · about
chapters (7)
- 0:00Start
- 8:28A service for templates?
- 17:12Per-user configuration for testing changes
- 19:36Parallel development of a site-wide redesign
- 20:39The thundering herd
- 21:17cached. Loader configuration
- 22:10Leverage version control
related talks
17mExemplar-y Backstage Templates
40mBuilding in Constrained Environments: Lessons from YouTrack Apps
11mAddressing deployment speed and developer focus
28mSharing is Caring… At Scale!
26mRapid Templating: "Designing in the Browser" with Sass, Compass, and Serve
18mDesigning and Deploying Internal Quarto Templates
52mThe Promise and Peril of Scriptable Software
40mJAMstack: Silly Name. Serious Stuff