How Your Architecture & Infrastructure Can Make or Break Your Team’s Productivity
summary
Claim: switching to a JAMstack decoupled front end plus precompiled assets and CDN deploys removes backend gatekeeping, cuts servers and runtime complexity, and enables one click rollbacks with immutable deploys. Use serverless functions for privileged API calls so front-end teams avoid owning middle tiers. Evidence: a production app on Netlify records 4 deploys in ~5 hours, showing sustained multiple-daily deploy velocity and fewer fragile releases.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:47Primary Goal as a Company Is To Ship Value to Customers Quickly
- 1:05What Stops a Team from Shipping
- 2:07How Complexity Can Affect the Team
- 4:16Decoupled Front Ends Reduce Complexity
related talks
51mJAMstack: Silly name, serious stuff
44mJAMstack: Web Apps at Ludicrous Speed
50mDo we really need this JAMstack thing? And what even is it?
05mLightning talk: Give a try to the JAM(stack)
31mJAMStack - The Total Victory of JavaScript
34mServing for the win - Deployments and hosting for the rest of us
31mThe post-Jamstack world and the rise of Hybrid Frameworks
30mRise of the Jamstack — Mathias Biilmann